I generally like Microsoft as a development stack, but this kerfuffle is reminding me of issues I've had trying to get the folks working on Graph API to understand why being able to access existing APIs with a different kind of credential than they currently support would be helpful.
If you're not familiar, there's two different ways to authenticate against Graph API - either directly with the user's credentials, which is good for webapps and user-interactive desktop stuff, and using application credentials, which are suited for server-side workers and daemons and things like that. All the Graph APIs have weird hodgepodges of permissions that are allowed, which sometimes make sense (getting the current user's profile at /me) and often don't make any sense at all, and are just not supported because they didn't bother.
If you've got a lot of time on your hands, you can whine and open UserVoice items and rally other people up and lobby, and sometimes they'll get off their asses and do something. Or not, like some of the Teams presence and calling APIs that have been unimplemented for three or four years now...
If you're not familiar, there's two different ways to authenticate against Graph API - either directly with the user's credentials, which is good for webapps and user-interactive desktop stuff, and using application credentials, which are suited for server-side workers and daemons and things like that. All the Graph APIs have weird hodgepodges of permissions that are allowed, which sometimes make sense (getting the current user's profile at /me) and often don't make any sense at all, and are just not supported because they didn't bother.
If you've got a lot of time on your hands, you can whine and open UserVoice items and rally other people up and lobby, and sometimes they'll get off their asses and do something. Or not, like some of the Teams presence and calling APIs that have been unimplemented for three or four years now...