Skip to content

[NAA] Update on how to check for online or on-premises accounts #5302

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

davidchesnut
Copy link
Member

Update on how to check for online or on-premises accounts

@davidchesnut davidchesnut requested a review from AlexJerabek July 28, 2025 15:26
Copy link
Contributor

Learn Build status updates of commit 25eb059:

✅ Validation status: passed

File Status Preview URL Details
docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md ✅Succeeded View

For more details, please refer to the build report.

Comment on lines +414 to +415
- For online accounts, the service will return a result with the ServerLocation key set to Exchange Online.
- For on-premise accounts, the service will not return a ServerLocation key.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding some formatting to draw attention to the distinctions in the bullet points. Also, I think ServerLocation should be in code ticks, but ignore that if it's not a code construct.

Suggested change
- For online accounts, the service will return a result with the ServerLocation key set to Exchange Online.
- For on-premise accounts, the service will not return a ServerLocation key.
- For **online** accounts, the service will return a result with the `ServerLocation` key set to Exchange Online.
- For **on-premise** accounts, the service will not return a `ServerLocation` key.

- For on-premise accounts, the service will not return a ServerLocation key.

> [!NOTE]
> For customers that use vanity URLs you need to specifically configure your add-in to call the Autodiscover service on the vanity URL endpoint.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> For customers that use vanity URLs you need to specifically configure your add-in to call the Autodiscover service on the vanity URL endpoint.
> For customers that use vanity URLs, you need to specifically configure your add-in to call the Autodiscover service on the vanity URL endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants