Follow up to MC1268930: Retirement of default app-only consistency in Microsoft Entra

Follow-up: Application IDs that may be impacted by the upcoming Entra Graph app-only consistency change

As a follow-up to our earlier communication (MC1268930, April '26) regarding the upcoming change to disable default app-only consistency for Microsoft Entra Graph APIs, we are providing a list of Application (Client) IDs (AppIDs) that may be impacted in your organization.

This information is being shared to help administrators identify where to look when reviewing applications that use app-only access with Microsoft Entra Graph APIs. Inclusion in this list does not necessarily indicate that an application will experience an issue, but it does highlight applications that may rely on the previous default consistency behavior.

How to use this information

• Use the AppIDs below to locate the corresponding applications in Microsoft Entra ID.
• Review whether these applications perform read or write operations immediately after a write using app-only tokens. Use the guidance here: Designing for Eventual Consistency for Microsoft Entra for removing dependency on this feature.
• Validate application behavior by testing with the request header ConsistencyLevel: Eventual.
• Prioritize validation and remediation before June 30, 2026, and during the scheduled scream test windows in July 2026.

What to expect next

• Temporary exclusions remain in place through June 30, 2026. No additional changes related to this feature will be deployed outside of the scheduled test windows prior to that date.

Potentially impacted Application IDs

a08effb0-6b76-4461-a884-5c4c22d19c0f

We recommend completing testing and any required updates ahead of the June 30, 2026 retirement date to avoid potential disruptions when the change becomes generally available.

For additional guidance, see:

• Designing for Eventual Consistency for Microsoft Entra
• Microsoft Entra architecture – Data consistency