NAA-SSO token supports GRAPH tokens only?

[glr0221]

Hello Team Microsoft.

As per your documentation, the old ways (getCallbackTokenAsync) of getting a REST or EXCHANGE token will be disabled on servers come October 2024. And NAA-SSO is an alternative way of getting tokens moving forward. You sample code features the way of getting GRAPH tokens using NAA-SSO.

However, the sample code does not show how we can get REST-enabled tokens using NAA-SSO. As you know some REST-enabled addins are allowed (exempted) to operate until sometime 2025. Is there a way to get REST-enabled tokens using NAA-SSO?

Thank you very much.

[AlexJerabek]

Thanks for raising this issue @glr0221.

@besiler, could you please weigh in here?

[mattgeim]

Sorry for the late response - I don't believe the extension would be included for a new App ID that would be registered as part of enabling NAA. Migration from Outlook REST / EWS to Microsoft Graph is the recommendation. Please let us know if there is a scenario that you are unable to accomplish with Graph and we can involve the appropriate teams to investigate.

[glr0221]

@mattgeim Thanks for the feedback. I do agree with you on the migration from REST to GRAPH. The major downside right now of the GRAPH API is that it cannot be used for mobile because it can't support SSO-OBO right now. NAA-SSO, if implemented on mobile, will most definitely push us to use GRAPH for all our addins. Will Identity API 1.3 be supported on mobile? Thanks.

[andrebel10]

I'm not clear on this. Can we use a token that we got from new NAA flows to access data on the managed EWS API? Or do we now 100% HAVE to use Graph?