Hi @Pete have you tried using a different App Registration? If the issue is indeed due to the new app registration that requires admin consent, you could consider using a different app registration that doesn’t require such consent.
Also if your container app logic allows it, request a more granular scope instead of api://<app-id>/.default
. Use a scope specific to your container app's needs, like:
-
api://<app-id>/read
(for read-only access) - A custom scope defined within your app registration (for specific actions)
- This way, your container app only requests the minimum permissions it needs, reducing potential conflicts.
Please let us know if you have future questions.