[all hosts] Reorg platforms, remove out-of-support versions (#4532)

* [all hosts] Reorg platforms, remove out-of-support versions

* Apply suggestions from code review

Co-authored-by: Sam Ramon <15154970+samantharamon@users.noreply.github.com>

---------

Co-authored-by: Sam Ramon <15154970+samantharamon@users.noreply.github.com>

docs/concepts/browsers-used-by-office-web-add-ins.md

@@ -2,7 +2,7 @@
 title: Browsers and webview controls used by Office Add-ins
 description: Specifies how the operating system and Office version determine what webview is used by Office Add-ins.
 ms.topic: concept-article
-ms.date: 10/31/2023
+ms.date: 04/24/2024
 ms.localizationpriority: medium
 ---
 
@@ -13,7 +13,7 @@ Office Add-ins are web applications that are displayed using iframes when runnin
 Which webview is used depends on:
 
 - The computer's operating system.
-- Whether the add-in is running in Office on the web, in Office downloaded from a Microsoft 365 subscription, or in perpetual Office 2013 or later.
+- Whether the add-in is running in Office on the web, in Office downloaded from a Microsoft 365 subscription, or in perpetual Office 2016 or later.
 - Within the perpetual versions of Office on Windows, whether the add-in is running in the "retail" or "volume-licensed" variation.
 
 > [!IMPORTANT]
@@ -23,7 +23,7 @@ Which webview is used depends on:
 >
 > We recommend (but don't require) that you continue to support these combinations, at least in a minimal way, by providing users of your add-in a graceful failure message when your add-in is launched in one of these webviews. Keep these additional points in mind:
 >
-> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [AppSource](/office/dev/store/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on the web on these browsers.
+> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [AppSource](/office/dev/store/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on these web browsers.
 > - AppSource still tests for combinations of platform and Office *desktop* versions that use Trident or EdgeHTML. However, it only issues a warning when the add-in doesn't support these webviews; the add-in isn't rejected by AppSource.
 > - The [Script Lab tool](../overview/explore-with-script-lab.md) no longer supports Trident.
 >
@@ -43,7 +43,7 @@ For these platforms, the platform alone determines the browser that is used.
 |Android|any|Chrome|
 
 > [!IMPORTANT]
-> [Conditional Access](/azure/active-directory/conditional-access/overview) is not supported for Office Add-ins on iOS or Android. Those add-ins use the Safari-based WKWebView or the Android-based WebView, not an Edge-based browser control.
+> [Conditional Access](/azure/active-directory/conditional-access/overview) isn't supported for Office Add-ins on iOS or Android. Those add-ins use the Safari-based WKWebView or the Android-based WebView, not an Edge-based browser control.
 
 ## Windows
 
@@ -57,7 +57,7 @@ An add-in running on Windows might use any of three different webviews:
 
 For perpetual versions of Office on Windows, the browser that is used is determined by the Office version, whether the license is retail or volume-licensed, and whether the Edge WebView2 (Chromium-based) is installed. The version of Windows doesn't matter, but note that Office Web Add-ins aren't supported on versions earlier than Windows 7 and Office 2021 isn't supported on versions earlier than Windows 10.
 
-To determine whether Office 2016 or Office 2019 is retail or volume-licensed, use the format of the Office version and build number. (For Office 2013 and Office 2021, the distinction between volume-licensed and retail doesn't matter.)
+To determine whether Office 2016 or Office 2019 is retail or volume-licensed, use the format of the Office version and build number. (For Office 2021, the distinction between volume-licensed and retail doesn't matter.)
 
 - **Retail**: For both Office 2016 and 2019, the format is `YYMM (xxxxx.xxxxxx)`, ending with two blocks of five digits; for example, `2206 (Build 15330.20264)`.
 - **Volume-licensed**:
@@ -73,7 +73,6 @@ To determine whether Office 2016 or Office 2019 is retail or volume-licensed, us
 | Office 2016 | Retail | Yes<sup>1</sup> | WebView2 (Microsoft Edge<sup>2</sup> Chromium-based) |
 | Office 2016 | Retail | No | EdgeHTML (Microsoft Edge Legacy)<sup>2, 3</sup></br>If Edge isn't installed, Trident+ (Internet Explorer 11) is used. |
 | Office 2016 | Volume-licensed | Doesn't matter | Trident+ (Internet Explorer 11) |
-| Office 2013 | Doesn't matter | Doesn't matter | Trident+ (Internet Explorer 11) |
 
 <sup>1</sup> On Windows versions prior to Windows 11, the WebView2 control must be installed so that Office can embed it. It's installed with perpetual Office 2021 or later; but it isn't automatically installed with Microsoft Edge. If you have an earlier version of perpetual Office, use the instructions for installing the control at [Microsoft Edge WebView2 / Embed web content ... with Microsoft Edge WebView2](https://developer.microsoft.com/microsoft-edge/webview2/).
 

docs/concepts/requirements-for-running-office-add-ins.md

@@ -1,7 +1,7 @@
 ---
 title: Requirements for running Office Add-ins
 description: Learn about the client and server requirements that an end user needs to run Office Add-ins.
-ms.date: 05/20/2023
+ms.date: 04/24/2024
 ms.localizationpriority: medium
 ---
 
@@ -26,7 +26,7 @@ For all types of add-ins (content, Outlook, and task pane add-ins and add-in com
 
 For content and task pane add-ins, in the supported Office client applications - Excel, PowerPoint, Project, or Word - you also need either an [app catalog](../publish/publish-task-pane-and-content-add-ins-to-an-add-in-catalog.md) on SharePoint to upload the add-in's XML manifest file, or you need to deploy the add-in using [Integrated Apps](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps).
 
-To test and run an Outlook add-in, the user's Outlook email account must reside on Exchange 2013 or later, which is available through Microsoft 365, Exchange Online, or through an on-premises installation. The user or administrator installs manifest files for Outlook add-ins on that server.
+To test and run an Outlook add-in, the user's Outlook email account must reside on Exchange 2016 or later, which is available through Microsoft 365, Exchange Online, or through an on-premises installation. The user or administrator installs manifest files for Outlook add-ins on that server.
 
 > [!NOTE]
 > POP and IMAP email accounts in Outlook don't support Office Add-ins.
@@ -36,8 +36,8 @@ To test and run an Outlook add-in, the user's Outlook email account must reside
 The following software is required for developing an Office Add-in for the supported Office desktop clients or web clients that run on Windows-based desktop, laptop, or tablet devices.
 
 - For Windows x86 and x64 desktops, and tablets such as Surface Pro:
-  - The 32- or 64-bit version of Office 2013 or a later version, running on Windows 7 or a later version.
-  - Excel 2013, Outlook 2013, PowerPoint 2013, Project Professional 2013, Project 2013 SP1, Word 2013, or a later version of the Office client, if you're testing or running an Office Add-in specifically for one of these Office desktop clients. Office desktop clients can be installed on premises or via Click-to-Run on the client computer.
+  - The 32- or 64-bit version of Office 2016 or a later version, running on Windows 7 or a later version.
+  - Excel 2016, Outlook 2016, PowerPoint 2016, Project Professional 2016, Project 2016, Word 2016, or a later version of the Office client, if you're testing or running an Office Add-in specifically for one of these Office desktop clients. Office desktop clients can be installed on premises or via Click-to-Run on the client computer.
 
   If you have a valid Microsoft 365 subscription and you don't have access to the Office client, you can [download and install the latest version of Office](https://support.microsoft.com/office/4414eaaf-0478-48be-9c42-23adc4716658).
 
@@ -71,17 +71,17 @@ Specifically for Outlook running on smartphones and non-Windows tablet devices,
 
 | Office application | Device | Operating system | Exchange account | Mobile browser |
 |:-----|:-----|:-----|:-----|:-----|
-|Outlook on Android|- Android tablets<br>- Android smartphones|- Android 4.4 KitKat or later|On the latest update of Microsoft 365 Apps for business or Exchange Online|Browser not applicable. Use the native app for Android.<sup>1</sup>|
-|Outlook on iOS|- iPad tablets<br>- iPhone smartphones|- iOS 11 or later|On the latest update of Microsoft 365 Apps for business or Exchange Online|Browser not applicable. Use the native app for iOS.<sup>1</sup>|
-|Outlook on the web (modern)<sup>2</sup>|- iPad 2 or later<br>- Android tablets |- iOS 5 or later<br>- Android 4.4 KitKat or later|On Microsoft 365, Exchange Online|- Microsoft Edge<br>- Chrome<br>- Firefox<br>- Safari|
-|Outlook on the web (classic)|- iPhone 4 or later<br>- iPad 2 or later<br>- iPod Touch 4 or later|- iOS 5 or later|On on-premises Exchange Server 2013 or later<sup>3</sup>|- Safari|
+|Outlook on the web (modern)<sup>1</sup>|<ul><li>iPad 2 or later</li><li>Android tablets</li></ul>|<ul><li>iOS 5 or later</li><li>Android 4.4 KitKat or later</li></ul>|On Microsoft 365, Exchange Online|<ul><li>Microsoft Edge</li><li>Chrome</li><li>Firefox</li><li>Safari</li></ul>|
+|Outlook on the web (classic)|<ul><li>iPhone 4 or later</li><li>iPad 2 or later</li><li>iPod Touch 4 or later</li></ul>|<ul><li>iOS 5 or later</li></ul>|On on-premises Exchange Server 2016 or later<sup>2</sup>|<ul><li>Safari</li></ul>|
+|Outlook on Android|<ul><li>Android tablets</li><li>Android smartphones</li></ul>|<ul><li>Android 4.4 KitKat or later</li></ul>|On the latest update of Microsoft 365 Apps for business or Exchange Online|Browser not applicable. Use the native app for Android.<sup>3</sup>|
+|Outlook on iOS|<ul><li>iPad tablets</li><li>iPhone smartphones|<ul><li>iOS 11 or later</li></ul>|On the latest update of Microsoft 365 Apps for business or Exchange Online|Browser not applicable. Use the native app for iOS.<sup>3</sup>|
 
 > [!NOTE]
-> <sup>1</sup> OWA for Android, OWA for iPad, and OWA for iPhone native apps have been [deprecated](https://support.microsoft.com/office/076ec122-4576-4900-bc26-937f84d25a4b).
+> <sup>1</sup> Modern Outlook on the web on iPhone and Android smartphones is no longer required or available for testing Outlook add-ins.
 >
-> <sup>2</sup> Modern Outlook on the web on iPhone and Android smartphones is no longer required or available for testing Outlook add-ins.
+> <sup>2</sup> Add-ins aren't supported in Outlook on Android, on iOS, and modern mobile web with on-premises Exchange accounts.
 >
-> <sup>3</sup> Add-ins aren't supported in Outlook on Android, on iOS, and modern mobile web with on-premises Exchange accounts.
+> <sup>3</sup> OWA for Android, OWA for iPad, and OWA for iPhone native apps have been [deprecated](https://support.microsoft.com/office/076ec122-4576-4900-bc26-937f84d25a4b).
 
 > [!TIP]
 > You can distinguish between classic and modern Outlook in a web browser by checking your mailbox toolbar.

docs/design/add-in-commands.md

@@ -94,10 +94,10 @@ You can specify that a tab is only visible on the ribbon in certain contexts, su
 
 Add-in commands are currently supported on the following platforms, except for limitations specified in the subsections of [Command capabilities](#command-capabilities) earlier.
 
+- Office on the web
 - Office on Windows (build 16.0.6769+, connected to a Microsoft 365 subscription)
 - Office on Mac (build 15.33+, connected to a Microsoft 365 subscription)
-- Office on the web
-- Office 2019 or later on Windows or Mac
+- Perpetual Office 2019 or later on Windows or on Mac
 
 > [!NOTE]
 > For information about support in Outlook, see [Outlook support notes](../develop/create-addin-commands.md#outlook-support-notes).

docs/design/add-in-icons-fresh.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # Fresh style icon guidelines for Office Add-ins
 
-The Office 2013+ (perpetual) versions of Office use Microsoft's Fresh style iconography. If you would prefer that your icons match the Monoline style of Microsoft 365, see [Monoline style icon guidelines for Office Add-ins](add-in-icons-monoline.md).
+Perpetual Office 2016 and later use Microsoft's Fresh style iconography. If you would prefer that your icons match the Monoline style of Microsoft 365, see [Monoline style icon guidelines for Office Add-ins](add-in-icons-monoline.md).
 
 ## Office Fresh visual style
 

docs/design/add-in-icons-monoline.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # Monoline style icon guidelines for Office Add-ins
 
-Monoline style iconography are used in Office apps. If you'd prefer that your icons match the Fresh style of perpetual Office 2013+, see [Fresh style icon guidelines for Office Add-ins](add-in-icons-fresh.md).
+Monoline style iconography are used in Office apps. If you'd prefer that your icons match the Fresh style of perpetual Office 2016 and later, see [Fresh style icon guidelines for Office Add-ins](add-in-icons-fresh.md).
 
 ## Office Monoline visual style
 

docs/design/add-in-icons.md

@@ -19,7 +19,7 @@ Many HTML containers contain controls with iconography. Use Fabric Core’s cust
 [Add-in commands](add-in-commands.md) add buttons, text, and icons to the Office UI. Your add-in command buttons should provide meaningful icons and labels that clearly identify the action the user is taking when they use a command. The following articles provide stylistic and production guidelines to help you design icons that integrate seamlessly with Office.
 
 - For the Monoline style of Microsoft 365, see [Monoline style icon guidelines for Office Add-ins](add-in-icons-monoline.md).
-- For the Fresh style of perpetual Office 2013+, see [Fresh style icon guidelines for Office Add-ins](add-in-icons-fresh.md).
+- For the Fresh style of perpetual Office 2016 and later, see [Fresh style icon guidelines for Office Add-ins](add-in-icons-fresh.md).
 
 > [!NOTE]
 > You must choose one style or the other and your add-in will use the same icons whether it's running in Microsoft 365 or perpetual Office.

docs/design/contextual-tabs.md

@@ -18,9 +18,9 @@ A contextual tab is a hidden tab control in the Office ribbon that's displayed i
 > [!IMPORTANT]
 > Custom contextual tabs are currently only supported on Excel and only on these platforms and builds.
 >
+> - Excel on the web
 > - Excel on Windows: Version 2102 (Build 13801.20294) or later.
 > - Excel on Mac: Version 16.53.806.0 or later.
-> - Excel on the web
 
 > [!NOTE]
 > Custom contextual tabs work only on platforms that support the following requirement sets. For more about requirement sets and how to work with them, see [Specify Office applications and API requirements](../develop/specify-office-hosts-and-api-requirements.md).

docs/develop/asynchronous-programming-in-office-add-ins.md

@@ -13,7 +13,7 @@ Why does the Office Add-ins API use asynchronous programming? Because JavaScript
 
 The names of all asynchronous methods in the API end with "Async", such as the `Document.getSelectedDataAsync`, `Binding.getDataAsync`, or `Item.loadCustomPropertiesAsync` methods. When an "Async" method is called, it executes immediately and any subsequent script execution can continue. The optional callback function you pass to an "Async" method executes as soon as the data or requested operation is ready. This generally occurs promptly, but there can be a slight delay before it returns.
 
-The following diagram shows the flow of execution for a call to an "Async" method that reads the data the user selected in a document open in the server-based Word or Excel. At the point when the "Async" call is made, the JavaScript execution thread is free to perform any additional client-side processing (although none are shown in the diagram). When the "Async" method returns, the callback resumes execution on the thread, and the add-in can the access data, do something with it, and display the result. The same asynchronous execution pattern holds when working with Office client applications on Windows or Mac.
+The following diagram shows the flow of execution for a call to an "Async" method that reads the data the user selected in a document open in the server-based Word or Excel. At the point when the "Async" call is made, the JavaScript execution thread is free to perform any additional client-side processing (although none are shown in the diagram). When the "Async" method returns, the callback resumes execution on the thread, and the add-in can the access data, do something with it, and display the result. The same asynchronous execution pattern holds when working with Office client applications on Windows or on Mac.
 
 ![Diagram showing the command execution interaction over time with the user, the add-in page, and the web app server hosting the add-in.](../images/office-addins-asynchronous-programming-flow.png)
 

docs/develop/automatically-open-a-task-pane-with-a-document.md

@@ -28,7 +28,7 @@ The autoopen feature is currently supported in the following products and platfo
 
 |Products|Platforms|
 |:-----------|:------------|
-|<ul><li>Word</li><li>Excel</li><li>PowerPoint</li></ul>|Supported platforms for all supported products:<ul><li>Office on Windows Desktop. Build 16.0.8121.1000+</li><li>Office on Mac. Build 15.34.17051500+</li><li>Office on the web</li></ul>|
+|<ul><li>Word</li><li>Excel</li><li>PowerPoint</li></ul>|Supported platforms for all supported products:<ul><li>Office on the web</li><li>Office on Windows (Build 16.0.8121.1000 or later)</li><li>Office on Mac (Build 15.34.17051500 or later)</li></ul>|
 
 ## Best practices
 

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md

@@ -190,7 +190,7 @@ When you add the **\<Runtime\>** element, you also specify a lifetime with a val
 
 ## About the shared runtime
 
-On Windows or Mac, your add-in will run code for ribbon buttons, custom functions, and the task pane in separate runtime environments. This creates limitations such as not being able to easily share global data, and not being able to access all CORS functionality from a custom function.
+On Windows or on Mac, your add-in will run code for ribbon buttons, custom functions, and the task pane in separate runtime environments. This creates limitations such as not being able to easily share global data, and not being able to access all CORS functionality from a custom function.
 
 However, you can configure your Office Add-in to share code in the same runtime (also referred to as a shared runtime). This enables better coordination across your add-in and access to the task pane DOM and CORS from all parts of your add-in.
 

docs/develop/convert-xml-to-json-manifest.md

@@ -19,7 +19,7 @@ There are three basic tasks to converting an add-in project from the XML manifes
 > [!NOTE]
 > 
 > - The unified manifest is a preview feature for Office Add-ins and is currently supported only for Outlook on Windows.
-> - Add-ins that use the unified manifest can be sideloaded only on Office version 16.0.16501.10000 or later.
+> - Add-ins that use the unified manifest can be sideloaded only on Office Build 16.0.16501.10000 or later.
 > - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
 > - If you [created the project with Teams Toolkit](teams-toolkit-overview.md) or with the "unified manifest" option in the [Office Yeoman Generator](yeoman-generator-overview.md), it already uses the unified manifest.
 

docs/develop/create-addin-commands-unified-manifest.md

@@ -9,13 +9,13 @@ ms.localizationpriority: medium
 
 Add-in commands provide an easy way to customize the default Office user interface (UI) with specified UI elements that perform actions. For an introduction to add-in commands, see [Add-in commands](../design/add-in-commands.md).
 
-This article describes how to configure the [Unified manifest for Microsoft 365 (preview)](unified-manifest-overview.md) to define add-in commands and how to create the code for [function commands](../design/add-in-commands.md#types-of-add-in-commands). 
+This article describes how to configure the [Unified manifest for Microsoft 365 (preview)](unified-manifest-overview.md) to define add-in commands and how to create the code for [function commands](../design/add-in-commands.md#types-of-add-in-commands).
 
 > [!TIP]
 > Instructions for creating add-in commands with the XML manifest are in [Create add-in commands with the XML manifest](create-addin-commands.md).
 
 > [!NOTE]
-> The unified manifest is currently supported only for Outlook Add-ins on Windows. It's in preview and not yet supported for production add-ins.
+> The unified manifest is currently supported only for Outlook add-ins on Windows. It's in preview and not yet supported for production add-ins.
 
 ## Starting point and major steps