A cloud-based identity and access management service for securing user authentication and resource access
Hi Jackie,
your function app in the AME tenant is getting a valid token, but when it presents it to the Microsoft tenant, a conditional access policy is blocking the request, resulting in the AADSTS53003 error.
The key issue is that the Conditional Access policy in the target Microsoft tenant is evaluating the login attempt from your function app and deciding to block it. Common reasons for this include
The policy requires a compliant device, and the Azure Function's managed identity isn't recognized as one.
The policy restricts access to specific locations (IP ranges), and the outbound IPs of your Function App aren't approved.
It requires Multi-Factor Authentication (MFA), which a managed identity cannot perform.
Since you mentioned you don't have rights to change the Conditional Access policies, you need to work with the administrator of the Microsoft tenant (the one with 72f988bf-86f1-41af-91ab-2d7cd011db47).
Provide them with the following details so they can create an exemption or modify the policy to allow your function app
The Service Principal of your function app's managed identity. They can find this by the client_id in your logs: 74cd4af2-cafa-41cd-a37f-b3e6156954b8.
The outbound IP addresses of your Azure Function App. You can find these in the Azure portal under your Function App's properties.
Ask the admin to create an exclusion in the Conditional Access policy for this specific service principal or its IP addresses.
You are correctly authenticated, but authorized. You must collaborate with the Microsoft tenant's admin to adjust their Conditional Access policy to grant your function app access.
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer