Forum Discussion
Misleading Error Message 53004
You are experiencing the same frustration I did and are being mislead by the same error message in my opinion. In my case, it was the account in my tenant trying to auth as a federated user into another tenant that triggered that error message, again, in my source tenant. When you checked for risky sign-ins, did you check in the user's source (Federated or guest) Tenant if they had a risky sign-in event or were you checking in your tenant where you are trying to share the resources from?
If you don't see a risky sign-in event in either tenant, I am not sure what else might be going on and my next step would be to open a support ticket. Again, where it me, I'd open it as an Azure auth incident be prepared for the likely hood of being bounced around from support group to support group for a month or two as you stay on top of them, not allowing them to close the incident and escalating as needed. It took me months to resolve this for our Tenant but I eventually got to a person who knew enough to give me a few clues to resolve it for myself.