Delay in changing Azure AD permissions for Microsoft Graph with certificate?

Viewed 1926

We're adding permissions in an Azure AD application for Microsoft Graph that doesn't seem to have any effect.

I tried to remove all permissions from another already working app and it still works without any permissions assigned all.

Is there any known delays when updating permissions? (We're using application permissions with certificates).

3 Answers

I can confirm that it seems to be a delay. After more than 2 hours and no changes it started working as expected.

With the v1 Endpoint, you can force changes to scopes by adding prompt=consent to your authentication URL.

Note that if the new permission requires Admin Consent, that will also need to be reapplied.

Sorry for the issue here Jonas. I'm assuming that you either went through a consent experience for your app (as Marc is indicated that you can force) OR that in the Azure Portal, after making app configuration changes, that you clicked on "Grant Permissions"? To be clear, changing app configuration only changes the permissions your app is requesting. These permissions still need to be granted (either through consent or in the app's tenant through the Grant Permissions button in the Azure Portal) - simply changing the app config does not re-grant permissions.

So assuming that permissions were re-granted, is this where you are seeing delays in the grant update taking place? If so, please can you send us the full error that you are seeing (client-request-id and timestamp) and we can take a look.

Hope this helps,

Related