Microsoft Office Azure AD Graph Migration: Is Administrator Action Required?
Question details
Administrators need to know if manual intervention is required to migrate the Microsoft Office application from retiring Azure AD Graph APIs to Microsoft Graph.
- Product
- Microsoft Office
- Device & OS
- not provided
- Scenario
- IT administrators are reviewing application dependencies following Microsoft's advisory to migrate from retiring Azure AD Graph APIs to Microsoft Graph.
- Observed behavior
- Microsoft Office (Application ID d3590ed6-52b3-4102-aeff-aad2292ab01c) is still flagged as using the legacy Azure AD Graph API, prompting confusion over required migration steps.
Verify the application ID in your Microsoft Entra ID admin center to confirm it matches the Microsoft Office application (d3590ed6-52b3-4102-aeff-aad2292ab01c).
Monitor for Updates and Rely on Microsoft Extended Access
No immediate administrator action is required for this specific Microsoft Office application, as Microsoft is actively developing a replacement and granting extended access.
Microsoft has confirmed that certain first-party applications, including Microsoft Office, Microsoft Visual Studio Legacy, and Microsoft Intune, currently do not have an update available that removes their dependency on Azure AD Graph.
To prevent service disruptions, Microsoft is automatically granting extended access to these affected applications while they build the necessary replacement versions for Microsoft Graph.
Log into the Microsoft Entra admin center and navigate to 'App registrations' to locate the Microsoft Office application with ID d3590ed6-52b3-4102-aeff-aad2292ab01c.
Check the API permissions tab to verify its current usage of Azure AD Graph, but do not attempt to manually delete or modify these permissions.
Leave the application configuration as-is. Attempting to force a manual migration for this specific first-party application may disrupt Microsoft Office services for your users.
Regularly check the Microsoft Entra and Azure AD Graph retirement official updates page for new guidance on when the Microsoft Graph replacement becomes available.
Simplify Your Workflow with WPS Office
Dealing with complex API migrations and legacy Microsoft integrations can be time-consuming for IT administrators. If you are looking for a reliable, lightweight, and hassle-free office suite for your team, consider WPS Office. It provides comprehensive productivity tools without the heavy backend administrative overhead.
- 1. Download the installer: Visit the official WPS Office website and click the 'Free Download' button to get the latest version.
- 2. Install the software: Run the downloaded executable file and follow the straightforward on-screen instructions to install the suite.
- 3. Start working seamlessly: Open WPS Office and immediately start creating or editing your existing Microsoft Office documents without any complex cloud configurations.

Frequently Asked Questions
Why is Microsoft Office still using Azure AD Graph?
Certain Microsoft-owned applications, including Microsoft Office and Visual Studio Legacy, have deep legacy integrations with Azure AD Graph and are still awaiting an official update to fully transition to Microsoft Graph.
Will my Office applications stop working when Azure AD Graph retires?
No. Microsoft is providing extended access for affected first-party applications like Microsoft Office to ensure they continue functioning while the necessary replacement updates are being developed.
What is the specific application ID for the affected Microsoft Office app?
The specific application ID commonly associated with this Azure AD Graph migration delay is d3590ed6-52b3-4102-aeff-aad2292ab01c.
Do administrators need to manually migrate this specific Office application?
Currently, no manual administrator action is required for this specific application ID. Microsoft advises ignoring it until further official guidance and replacement updates are released.




