We have been struggling to add permissions in our app and the escalation team is also not helpful at all

Question

We have successfully registered an app on the Azure portal but encountered challenges when attempting to integrate two crucial graph scopes into our application:

EAS.AccessAsUser.All and EWS.AccessAsUser.All.

These scopes require user permission during the sign-in process via our app.

Despite raising this issue a month ago, it only recently received attention from the technical team a few days ago. Regrettably, the experience has been frustrating, with individuals in the email conversation displaying unprofessional behavior and failing to provide adequate assistance. If needed, I can provide detailed evidence of these interactions, including email exchanges and screenshots.

While the technical team shared a helpful article (https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-authenticate-an-ews-application-by-using-oauth), it did not address our specific issue. We are utilizing Microsoft Graphs and attempting to incorporate Delegated permissions for the mentioned scopes.

After reviewing the provided article and conducting additional tests, we found that a test app created from a different account successfully functioned with the same scope. This indicates that the issue may be isolated to the current account.

We have previously set up multiple apps without encountering such obstacles, making the current situation perplexing. Should you require any further information, please do not hesitate to reach out. We appreciate your attention to this matter.

Furthermore, we kindly request Microsoft's intervention regarding the behavior of the individuals tagged in our ticket. Their unprofessional conduct has only exacerbated our difficulties, and we urge appropriate action to prevent similar experiences for others.

Answer 1

Please email me the ticket number to ninob AT microsoft DOT com. I suspect that the ticket is in the wrong place (and was not sent to the developer team). Regular support will not be able to help with this, let's see if I can get the ticket to the right team.

Obviously - no excuse for communication issues you have seen; sigh. Sorry about that!