Merge pull request #5448 from OfficeDev/m365-icon-guidance

[All Hosts] (devx) fixing problems with cross-repo includes

Author: Rick-Kirkham

docs/design/add-in-icons.md

@@ -1,7 +1,7 @@
 ---
 title: Icon guidelines for Office Add-ins
 description: Get an overview of how to design icons and the Fresh and Monoline design styles for add-in commands.
-ms.date: 08/18/2023
+ms.date: 11/03/2025
 ms.topic: overview
 ms.localizationpriority: medium
 ---
@@ -10,6 +10,9 @@ ms.localizationpriority: medium
 
 Icons are the visual representation of a behavior or concept. They are often used to add meaning to controls and commands. Visuals, either realistic or symbolic, enable the user to navigate the UI the same way signs help users navigate their environment. They should be simple, clear, and contain only the necessary details to enable customers to quickly parse what action will occur when they choose a control.
 
+> [!NOTE]
+> This article about designing icons for ribbon buttons. For guidance about icons that represent the add-in in the app  acquisition and managment UIs of Microsoft 365 applications, see [Design icons for add-in acquisisiton and management](microsoft-365-extension-management-icons.md).
+
 Office app ribbon interfaces have a standard visual style. This ensures consistency and familiarity across Office apps. The guidelines will help you design a set of PNG assets for your solution that fit in as a natural part of Office.
 
 Many HTML containers contain controls with iconography. Use Fabric Core’s custom font to render Office styled icons in your add-in. The icon font provided by [Fabric Core](fabric-core.md) contains many glyphs for common Office metaphors that you can scale, color, and style to suit your needs. If you have an existing visual language with your own set of icons, feel free to use it in your HTML canvases. Building continuity with your own brand with a standard set of icons is an important part of any design language. Be careful to avoid creating confusion for customers by conflicting with Office metaphors.

docs/design/microsoft-365-extension-management-icons.md

@@ -0,0 +1,19 @@
+---
+title: Design icons for add-in acquisition and management
+description: Get design guidance for the icons that represent an add-in in the UIs for app acquisition and managment.
+ms.date: 11/03/2025
+ms.topic: best-practice
+ms.localizationpriority: medium
+---
+
+# Design icons for add-in acquisisiton and management
+
+An Office add-in is an App for Microsoft 365, just as are Teams apps and Copilot extensions. If the add-in uses the [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md), then it must conform to the requirements for Microsoft 365 extensions. In particular, it must have two icons that represent it in the app acquisition and managment UI of Teams, Office, Copilot, and other Microsoft 365 applications. 
+
+> [!NOTE]
+>
+> - This article isn't relevant to add-ins that use the [add-in only manifest](../develop/xml-manifest-overview.md). 
+> - This article *isn't* about designing icons for an add-in's ribbon buttons. For guidance about those, start with [Icon guidelines for Office Add-ins](add-in-icons.md).
+> - For guidance about designing icons that represent an add-in Microsoft Marketplace, see [Create an icon for your add-in](/partner-center/marketplace-offers/create-effective-office-store-listings#create-an-icon-for-your-add-in).
+
+[!INCLUDE [Microsoft 365 icon design guidance](~/../reusable-content/microsoft-365-development/includes/design-microsoft-365-extension-icons.md)]