Microsoft 365 Admin Center Marketplace and Purchase Services node name change
Starting December 2025, the Microsoft 365 Admin Center will replace the Purchase Services node with a new Marketplace node as a Level 1 item above Billing. This visual update affects global and billing admins, requires no action, and involves no changes to functionality or permissions. Introduction Microsoft 365 Admin CenterMarketplaceBillingPurchase Services When this will happen: How this affects your organization: Who is affected: Global and billing admins in SMEC and Enterprise environments who currently access the Purchase Services node in the Microsoft 365 Admin Center.(Note: SMB customers already see Marketplace in this location.) What will happen: The Purchase Services node will be retired. A new Marketplace node will appear as a Level 1 (L1) item above Billing in the left-hand navigation. This is a visual and navigational update only. No changes to functionality, permissions, or user workflows. The update will be applied by default; no admin action is required. What you can do to prepare: Inform helpdesk or support teams of the updated navigation label and location. Update internal documentation if it references Purchase Services or its previous location. Review the Marketplace experience to ensure familiarity with the updated placement. Learn more: Microsoft 365 admin center – Overview – Microsoft 365 admin | Microsoft Learn (documentation will be updated closer to rollout) Compliance considerations: Message ID: MC1177178
The post Microsoft 365 Admin Center Marketplace and Purchase Services node name change appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Microsoft 365 Admin Center Marketplace and Purchase Services node name change
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
External messaging limits for onmicrosoft.com-only organizations in Microsoft Teams
Microsoft Teams will impose outbound external messaging limits starting mid-September 2026 for organizations using only the default onmicrosof...
Microsoft Teams: Enable agents for existing applications in your organization
For third-party applications already being used in your organization, admins can now discover and enable the corresponding Teams agents from w...
Microsoft Viva: Campaigns Hub in Engage and Engage in Teams mobile
The Campaigns Hub in Viva Engage provides a centralized mobile destination where employees can discover and participate in organizational camp...
Planner: Conditional Coloring
Conditional Coloring highlight tasks based on selected criteria, making priorities, status, and important task details easier to spot. Product...
Outlook: Offline settings “Days of email to save” admin policy
Tenant admins will be able to define the default value for “Days of email to save” in Offline settings and designate whether end u...
Microsoft Copilot Studio: Agent Sharing amongst makers
Enables sharing of agents with other makers in the new GHCP harness. Makers can grant other makers Agent Viewer (view analytics/evaluations on...
OneDrive Photos on Windows: admin controls and policy support
OneDrive Photos, integrated into the OneDrive sync app for Windows 10/11, is currently available only for personal Microsoft accounts, with wo...
Admin app retiring in Teams, Outlook and Microsoft365.com
The Admin app for very small businesses in Teams, Outlook, and Microsoft365.com will retire by October 2026, with rollout starting August 2026...
Calls popout into a new window on the browser to support multi-tasking and collaboration during a meeting
Microsoft Teams for Web will introduce a Picture-in-Picture Call Monitor in October 2026, allowing users to manage meeting controls in a separ...
Microsoft Windows Autopatch: September 2026 Windows security update requires a restart for hotpatch-enabled devices
The September 2026 Windows security update requires a restart for hotpatch-enabled devices because it is a standard update. Devices will remai...