Merge branch 'main' into sharik-LHSalesAdvisor

Author: SKjerland

.github/workflows/StaleBranch.yml

@@ -2,6 +2,7 @@ name: (Scheduled) Stale branch removal
 
 permissions:
   contents: write
+  pull-requests: read
 
 # This workflow is designed to be run in the days up to, and including, a "deletion day", specified by 'DeleteOnDayOfMonth' in env: in https://github.com/MicrosoftDocs/microsoft-365-docs/blob/workflows-prod/.github/workflows/Shared-StaleBranch.yml.
 # On the days leading up to "deletion day", the workflow will report the branches to be deleted. This lets users see which branches will be deleted. On "deletion day", those branches are deleted.

.openpublishing.redirection.admin.json

@@ -1,12 +1,12 @@
 {
   "redirections": [
-    {
+        {
       "source_path": "microsoft-365/admin/manage/manage-plugins-for-copilot-in-integrated-apps.md",
       "redirect_url": "/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps",
       "redirect_document_id": false
     },
     {
-      "source_path": "microsoft-365/admin/manage/servicenow-aad-oauth-token.md",
+      "source_path": "microsoft-365/admin/manage/servicenow-aad-oauth-token-v1.md",
       "redirect_url": "/microsoft-365/admin/manage/servicenow-authentication",
       "redirect_document_id": false
     },

copilot/multiple-account-access.md

@@ -13,7 +13,7 @@ ms.collection:
 - m365copilot
 - magic-ai-copilot
 hideEdit: true
-ms.date: 04/24/2025
+ms.date: 04/29/2025
 ---
 
 # Multiple account access to Copilot for work and school documents
@@ -57,7 +57,6 @@ To configure this policy setting, you need to use [Cloud Policy service for Micr
 
 > [!NOTE]
 > - The policy setting is available in Cloud Policy as of January 30, 2025.
-> - Currently the policy setting is only available in English. But we’re working on making the localized versions available as soon as we can.
 > - Microsoft 365 GCC customers can see the policy setting in Cloud Policy, but the policy has no effect on them because multiple account access to Copilot is always disabled for Microsoft 365 GCC customers.
 
 If you enable or don't configure this policy setting, your users can use Copilot on work and school documents with a Copilot license that is from outside your organization.

copilot/release-notes.md

@@ -454,20 +454,6 @@ items:
              href: manage/servicenow-troubleshooting.md
            - name: Integrate Microsoft 365 with ServiceNow Virtual Agent
              href: manage/servicenow-virtual-agent-integration.md
-           - name: Microsoft 365 support integration guide for version 1.0.11 and earlier 
-             items:
-              - name: Configuration overview
-                href: manage/servicenow-overview-v1.md
-              - name: Configure basic authentication
-                href: manage/servicenow-basic-authentication-v1.md
-              - name: Configure Microsoft 365 support integration with Microsoft Entra auth Token
-                href: manage/servicenow-aad-oauth-token-v1.md
-              - name: Testing the configuration
-                href: manage/servicenow-testing-the-configuration-v1.md
-              - name: Troubleshooting
-                href: manage/servicenow-troubleshooting-v1.md
-              - name: Integrate Microsoft 365 with ServiceNow Virtual Agent
-                href: manage/servicenow-virtual-agent-integration-v1.md
     - name: Manage subscriptions and billing
       href: ../commerce/index.yml
     - name: Secure your organization

microsoft-365/admin/TOC.yml

@@ -33,10 +33,7 @@ On the Microsoft 365 **Active teams and groups** page, you can create groups of
 User management administrators have permissions to create, edit, or delete security groups; for more information about administrator roles, see [Assigning admin roles](../add-users/assign-admin-roles.md).
 
 There are also [Groups in Exchange Online and SharePoint Online](#groups-in-exchange-online-and-sharepoint-online) that you can use to send email or assign permissions to a group of users, and [Groups in Exchange Online and SharePoint Online](#groups-in-exchange-online-and-sharepoint-online) that grant users rights and access to sites and site collections.
-  
-> [!IMPORTANT]
-> Planning on using site mailboxes? All the users that are added to a SharePoint site via a security group rather than being added individually can use only the site mailbox from SharePoint. These users won't be able to access the site mailbox from Outlook. For more information, see [Use Microsoft 365 Groups instead of Site Mailboxes](https://support.microsoft.com/office/737d6b1f-67cc-41fe-8db8-f2d09dd1673b).
-  
+
 ## Manage security groups in the admin center
 
 ### Add a security group
@@ -83,7 +80,7 @@ If you want to create groups of users so you can send email to them all at the s
 
 - **Distribution group**: Used to distribute messages to a group of users. It's also called a  *mail-enabled distribution group*, or, a  *distribution list*. For more information, see [Manage distribution groups](/exchange/recipients-in-exchange-online/manage-distribution-groups/manage-distribution-groups).
 
-- **Security group**: Can be used to distribute messages to a group of users, or to grant access permissions to resources. This group is also called a *mail-enabled security group*. For more information, see [Manage mail-enabled security groups](/Exchange/recipients/mail-enabled-security-groups).
+- **Security group**: Can be used to distribute messages to a group of users, or to grant access permissions to resources. This group is also called a *mail-enabled security group*. For more information, see [Manage mail-enabled security groups](/exchange/recipients-in-exchange-online/manage-mail-enabled-security-groups).
 
 - **Dynamic distribution group**: A type of distribution group whose list of recipients is recalculated every time you send a message based on filters and conditions that you define. For more information, see [Manage dynamic distribution groups](/Exchange/recipients/dynamic-distribution-groups/dynamic-distribution-groups).