-1

Have some serious doubt as to what to use when implementing Outlook REST API for processing mails of users...

Regarding OAuth2 URL:

the php client example specifies "https://login.microsoftonline.com"

but the msdn docs specifies "https://login.live.com/oauth20_token.srf"

Regarding OAUTH2 Scopes:

Also regarding the Scope for enabling our app to use offline access for accessing the user's data anytime,

The Stack overflow Answer Specifies "offline_access" scope

whereas msdn scope docs1 and msdn scope docs2 Specifies "wl.offline_access" scope


I'm confused... will the support be dropped for any of the above spec attributes at any point of time? will my app stop working if they stop supporting it or is any of the above mentioned spec attributes expired/deprecated?

Plzzzz someone clarify this to me

Community
  • 1
  • 1
Crystal Paladin
  • 579
  • 5
  • 26
  • when including `wl.offline_access` scope in outlook rest api oauth2 flow, the microsoft login page reported an error, but after removing the `wl.offline_access` scope, the normal flow continued... So `offline_access` would be the right scope... – Crystal Paladin Feb 29 '16 at 12:58
  • 1
    The guys who downvoted this question at-least leave a comment why it deserved to be downvoted!... – Crystal Paladin Sep 04 '17 at 04:32

1 Answers1

1

The Outlook REST API is tested and supported with the Azure OAuth implementation, so I would definitely go with the login.microsoftonline.com and offline_access. The other docs you are citing are part of the Live SDK, which I believe would not work for Office 365 users.

Jason Johnston
  • 17,194
  • 2
  • 20
  • 34