m365 tenant status list fails, uses deprecated API
See original GitHub issueWhen using v5.0.0 of the M365 CLI, the command:
m365 tenant status list
yields:
Error: Please use MSGraph to access this resource https://docs.microsoft.com/en-us/graph/api/resources/service-communications-api-overview?view=graph-rest-1.0&preserve-view=true
I believe the CLI is using the old API that is now deprecated and should be using the Graph API for this status information.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Upcoming API Deprecations in Exchange Web Services for ...
Today we are announcing the deprecation of the 25 least used APIs of EWS for Exchange Online (as determined by the call volume...
Read more >API Deprecations Signal the Demise of Exchange Web Services
Exchange Web Services APIs due for deprecation by March 31, 2022 ... EWS is used inside their tenants and draw up plans for...
Read more >Microsoft Is Moving the Office 365 Service Communications ...
Microsoft is moving the Office 365 Service Communications API to the Microsoft Graph. The new API is in public preview.
Read more >Exchange API permissions missing | Blog - Vasil Michev
0. This will result in two changes for developers. First, we will retire the OAuth Sandbox by December 31, 2020. Additionally, we have...
Read more >Creating Connections to Microsoft Office 365
In addition, Microsoft Office 365 (deprecated) will not appear as a Source ... The Microsoft 365 connector uses a pre-registered multi-tenant app that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great to hear that you are unblocked! Again, apologies for the inconvenience this may have caused.
Thank you for raising this, I’ve had a quick look through the Graph API docs and it looks like this information is no longer provided, whilst we can’t resolve this we can make the Graph team aware of this.
…except for one thing… the old method returned a StatusTime field, listing the time the service left serviceOperational status. I don’t see that in the Graph version of this call (the serviceHealth objects only have id, service and status). Given that it’s not in Graph, there’s probably no work-around for this, but I thought I’d mention it. Thanks again!