question

Office365Dev-8057 avatar image
0 Votes"
Office365Dev-8057 asked KyleXu-MSFT commented

EWS Token Authority and Other Endpoints

Hi Team,

We have build an application to fetch mails using EWS client services. Have few queries which need clarification from you

  1. Regarding Initial Authorization

We are using below url for Authorization after app registration

EWS_URL = "https://login.windows.net/%s/oauth2/v2.0/authorize?scope=EWS.AccessAsUser.All+offline_access+openid+profile&response_type=code&client_id=%s&prompt=select_account&redirect_uri=%s" -> [ tenentid, clientid, redirecturl ]

and "https://login.microsoftonline.us/organizations/" for building PublicClientApplication.

Does "https://login.windows.net" correctly redirect to respective Token authority based on App Registration portal and based on Azure Native Cloud? or is it better, we explicitly specify the Token authority based on Endpoints mentioned in App Registration page in both cases?

ex : Worldwide - https://login.microsoftonline.com/organizations/
US GCC HIGH - https://login.microsoftonline.us/organizations/

  1. Extend functionality for All Azure Native Clouds

We are planning to extend the application to support other Azure Native Clients and planning to configure below end points to get correct Token authority and EWS endpoints. Is our understanding is correct in identifying these endpoints? Also, do you have a standard recommendation here other than this.

118666-image.png




Your help and advice is highly appreciated.

Regards,









office-exchange-server-dev
image.png (14.8 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@Office365Dev-8057

The using of EWS is related with Exchange development, so I help you change the tag to "office-exchange-server-dev".

1 Vote 1 ·

0 Answers