Merge pull request #29377 from MicrosoftDocs/main

[AutoPublish] main to live - 09/05 13:30 PDT | 09/06 02:00 IST

Author: m365-skilling-repo-management[bot]

microsoft-365/admin/manage/manage-shared-agents.md

@@ -5,7 +5,7 @@ f1.keywords:
 ms.author: erikre
 author: ErikRe
 manager: dansimp
-ms.date: 08/13/2025
+ms.date: 09/04/2025
 ms.update-cycle: 180-days
 audience: Admin
 ms.topic: concept-article
@@ -79,9 +79,32 @@ If you need to restore access to a previously blocked agent, you can unblock it
 
 After the agent is unblocked, it’ll be restored to the most recent availability and deployment state.
 
+## Ownerless shared agent management
+
+Shared agents may become ownerless when the user who created them is deleted from the organization.
+
+To help administrators manage these scenarios, the Microsoft 365 Admin Center now enables you to identify and manage ownerless shared agents. The dashboard displays the total count of such agents, a one-click filter to quickly isolate them, and real-time updates reflecting user deletions, enabling administrators to efficiently review and address ownership gaps by blocking or deleting affected agents.
+
+:::image type="content" source="../../media/agents/ownerless-shared-agents.png" alt-text="Screenshot showing ownerless shared agents." lightbox="../../media/agents/unblock.png":::
+
+### Key features
+
+- Ownerless agent count: Administrators can now view the total number of agents without a valid owner directly from the dashboard. For example, the dashboard shows 20 ownerless agents indicating that these agents were created by users who have since left the organization.
+
+- One-Click Filter: Clicking the dashboard pane instantly filters the agent inventory to display only shared agents missing an owner. This feature allows for quick triage and action.
+
+- Real-Time Updates: The ownerless agent count is automatically updated when a user is hard deleted from the organization. This feature ensures that the dashboard reflects the current state without requiring manual refreshes.
+
+### Steps to view and manage ownerless shared agents
+
+1. In the admin center, go to **Copilot** > **Agents**.
+2. Locate the **Missing an Owner** tab.
+3. Select the tab to filter **Agent inventory**.
+4. Review the list of ownerless agents and take appropriate actions such as blocking or deleting the agent.
+
 ## Export to Excel
 
-You can export the list of shared agents to an Excel file. This is essential for detailed analysis and reporting. 
+You can export the list of shared agents to an Excel file. This feature is essential for detailed analysis and reporting.
 
 > [!NOTE]
 > If the export process reaches one minute, only the data up to that point will be included in the exported file.

microsoft-365/media/agents/ownerless-shared-agents.png

@@ -80,3 +80,8 @@ items:
 
             - name: Microsoft 365 Backup
               href: ../backup/backup-overview.md
+
+    - name: Troubleshooting
+      items:
+            - name: RequestDisallowedByPolicy
+              href: error-request-disallowed-by-policy.md

microsoft-365/media/services/azure-allowed-resource-types.png

@@ -0,0 +1,62 @@
+---
+title: RequestDisallowedByPolicy 
+ms.author: chucked
+author: chuckedmonson
+manager: jtremper
+ms.reviewer: ivchenya
+ms.date: 09/05/2025
+audience: admin
+ms.topic: install-set-up-deploy
+ms.service: microsoft-365-business
+ms.subservice:
+search.appverid: 
+ms.collection: 
+ms.localizationpriority:  medium
+description: Learn how to fix the RequestDisallowedByPolicy error when creating resources in Azure.
+---
+
+# RequestDisallowedByPolicy
+
+This article describes how to fix the **RequestDisallowedByPolicy** error when creating resources in Azure.
+
+If you’re seeing the error code **RequestDisallowedByPolicy**, it means that the creation of a resource was blocked by an Azure policy assigned in your environment. This often occurs when certain resource types aren't explicitly allowed under a policy—such as the GM Resource Standards policy.
+
+## What’s causing the issue?
+
+Your organization has applied a policy, typically called "Allowed resource types"—to control which Azure resources can be created. If you're trying to deploy a resource type that's not listed in this policy, Azure blocks the request and show this error.
+
+## How to resolve it
+
+To fix this, you need to update the policy assignment to include the resource types you're trying to deploy (for example, for document processing for Microsoft 365 scenarios).
+
+### Step-by-step instructions
+
+1. Sign in to the [Azure portal](https://portal.azure.com/).
+
+2. In the top search bar, type *Policy* and select it.
+
+3. In the Policy blade, select **Assignments** from the left navigation.
+
+4. Locate the policy assignment with the name "Allowed resource types" (usually tied to the GM Resource Standards initiative).
+
+5. Select the policy, and then select **Edit assignment**.
+
+6. Under **Parameters**, add the resource types you want to allow:
+    - Microsoft.Syntex/accounts
+    - Microsoft.Syntex/documentProcessors
+
+7. Select **Save** to apply the changes.
+
+8. Try creating the resource again.
+
+Need visual help?
+
+Check out the following screenshots for each step in the Azure portal to guide you through the process.
+
+![Screenshot showing the Assign policy page in the Azure portal.](../media/services/azure-assign-policy.png)
+
+![Screenshot showing the Policy Assignments page in the Azure portal.](../media/services/azure-assign-policy.png)
+
+![Screenshot showing the Allowed resource types page in the Azure portal.](../media/services/azure-assign-policy.png)
+
+![Screenshot showing the Assign policy page for a specific policy in the Azure portal.](../media/services/azure-assign-policy-full-page.png)