MicrosoftI guess you all missed this part:
Some Microsoft applications, including Microsoft Office, Microsoft Visual Studio Legacy, and Microsoft Intune, do not yet have an update available without Azure AD Graph API usage. For these, we will provide future Azure AD Graph API retirement blog updates when a replacement version is available. These apps will be granted extended access for Azure AD Graph and sufficient time will be given to update the applications when an update is made available.
Probably because we are all searching around for the object ID in a vain attempt to get some useful information - searching for "Microsoft Office" is a bit too vague these days.
We now in the situation where we have an error and need to remember at some unknown point in the future to go and look at a long forgotten blog..
Yep...but yet another example of Microsoft's inability to get things fixed before telling everyone the sky is falling. I.e., fix their own stuff before sending out unnecessary notices.
Yep...but yet another example of Microsoft's inability to get things fixed before telling everyone the sky is falling. I.e., fix their own stuff before sending out unnecessary notices.
Counterpoint: They are giving you an even longer heads-up while they are working on updating their own applications, so you have even more time to fix yours. Microsoft is not just one giant team. There are different teams working on different products, and some of those teams (Office, Intune) are customers of other teams (Graph API). What would be the point in them waiting until the Office and Intune teams fix their dependencies before letting you know about the dependencies that you can get started on fixing? But I get it... "Microsoft bad".
