Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAA Incompatibility with Require Approved Client App Grant Conditional Access Policy #5315

Closed
AzGuineaPig opened this issue Jan 27, 2025 · 3 comments
Assignees
Labels
Area: authentication Issue related to authentication Needs: author feedback Waiting for author (creator) of Issue to provide more info Status: no recent activity Issue or PR is stale (no recent activity)

Comments

@AzGuineaPig
Copy link

We have an Office add-in for Outlook mobile that utilizes NAA via msal-browser and createNestablePublicClientApplication on iOS and Android devices. However, when attempting to fetch a token, we encounter the error message “You can’t get there from here” with the sign-in error code 530021. This error indicates that the application does not meet the conditional access approved app requirements.

This failure is triggered by a Conditional Access policy with the following settings:

Users: All users
Target Resources: Office 365 Exchange Online (00000002-0000-0ff1-ce00-000000000000)
Conditions:
Device Platforms: iOS and Android
Client Apps: Mobile apps and desktop clients
Grant :
Grant Access : Require approved client app

When requesting a token with a mail scope on a mobile device, the error occurs. If the token does not include a mail scope, it works fine, likely because it does not target the Exchange Online resource specified in the policy.

Attempts to add an exception to the Conditional Access policy for our app registration have been unsuccessful. It seems that the exception applies to applications accessing the app registration resource, not to the app registration requesting a token.

Is there any way to resolve this issue or change the token request method? The MSAL documentation does not provide a solution. If this issue persists, Office Add-ins using NAA (replacing EWS/REST) may not be able to comply with the “Require approved client app” policy, causing compliance issues for customers who restrict access to Exchange Online resources to approved client apps. Although the add-in is launched from an approved client app (Outlook), it is treated as a separate app.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Jan 27, 2025
@slabereemsft slabereemsft self-assigned this Jan 31, 2025
@slabereemsft slabereemsft added Area: authentication Issue related to authentication Type: product feature request Office JS ideas that should be posted to aka.ms/m365dev-suggestions (formerly User Voice.) and removed Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP labels Jan 31, 2025
@davidchesnut
Copy link
Member

Hi @AzGuineaPig,

Sorry for the slow response on this. NAA doesn't support the approved client app policy as it will be retired March 2026. Admins should move to the application protection policy grant. Full details on how to do this are documented in Migrate approved client app to application protection policy in Conditional Access.

Cheers,
David

@davidchesnut davidchesnut added Needs: author feedback Waiting for author (creator) of Issue to provide more info and removed Type: product feature request Office JS ideas that should be posted to aka.ms/m365dev-suggestions (formerly User Voice.) labels Mar 6, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: no recent activity Issue or PR is stale (no recent activity) label Mar 10, 2025
Copy link
Contributor

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

Copy link
Contributor

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: authentication Issue related to authentication Needs: author feedback Waiting for author (creator) of Issue to provide more info Status: no recent activity Issue or PR is stale (no recent activity)
Projects
None yet
Development

No branches or pull requests

3 participants