From 25eb0590273f48a1d23c53e9eb5bc1aff99b6832 Mon Sep 17 00:00:00 2001 From: David Chesnut Date: Mon, 28 Jul 2025 08:14:50 -0700 Subject: [PATCH 1/2] Updated info on checking online or on-prem account --- .../faq-nested-app-auth-outlook-legacy-tokens.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md b/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md index 1a11854990..3668ff880d 100644 --- a/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md +++ b/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md @@ -4,7 +4,7 @@ description: Nested app authentication and Outlook legacy tokens deprecation FAQ ms.service: microsoft-365 ms.subservice: add-ins ms.topic: faq -ms.date: 07/11/2025 +ms.date: 07/28/2025 --- # Nested app authentication and Outlook legacy tokens deprecation FAQ @@ -407,6 +407,16 @@ You can determine if the signed-in user has an Exchange Online account or on-pre > [!NOTE] > Support for Outlook 2016 and Outlook 2019 ends October 2025. For more information, see [End of support for Office 2016 and Office 2019](https://support.microsoft.com/office/818c68bc-d5e5-47e5-b52f-ddf636cf8e16). +The **accountType** property requires mailbox requirement set 1.6. On older Outlook clients you’ll need to use the Autodiscover service as follows. + +Call the Autodiscover endpoint for the outlook.office365.com domain. `https://outlook.office365.com/autodiscover/autodiscover.json/v1.0/{email}?Protocol=EWS&ServerLocation=true` + +- 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. + +> [!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. + ### How do I deploy my add-in to Microsoft AppSource If you're publishing a new add-in to Microsoft AppSource, it will need to go through a certification process. For more information, see [Publish your Office Add-in to Microsoft AppSource](../publish/publish-office-add-ins-to-appsource.md). If you're updating the manifest of an add-in that is already published to Microsoft AppSource, you need to go through the certification process again. You can update the add-in's source code on your web server any time without a need to go through the certification process. From 5d012e52dfea8aaa21324d15455199b23d552ec1 Mon Sep 17 00:00:00 2001 From: David Chesnut Date: Tue, 5 Aug 2025 09:38:11 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Alex Jerabek <38896772+AlexJerabek@users.noreply.github.com> --- docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md b/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md index 3668ff880d..a20cc103c6 100644 --- a/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md +++ b/docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md @@ -411,11 +411,11 @@ The **accountType** property requires mailbox requirement set 1.6. On older Outl Call the Autodiscover endpoint for the outlook.office365.com domain. `https://outlook.office365.com/autodiscover/autodiscover.json/v1.0/{email}?Protocol=EWS&ServerLocation=true` -- 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. > [!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. +> For customers that use vanity URLs, you need to specifically configure your add-in to call the Autodiscover service on the vanity URL endpoint. ### How do I deploy my add-in to Microsoft AppSource