From 77ee8828398895a2c5f88fa4b693bf212e9d84af Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 16 Jan 2025 16:45:27 -0600 Subject: [PATCH 01/16] Update ownerless-groups-teams.md Major update to ownerless group policy doc that includes common FAQs without using the FAQ format --- .../create-groups/ownerless-groups-teams.md | 119 ++++++++++++++---- 1 file changed, 95 insertions(+), 24 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 978e3ebe01b..f813d29109a 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -1,7 +1,7 @@ --- -title: "Manage ownerless Microsoft 365 groups and teams" +title: Manage ownerless Microsoft 365 groups and teams ms.reviewer: rahulnayak -ms.date: 06/27/2024 +ms.date: 01/16/2025 f1.keywords: NOCSH author: DaniEASmith ms.author: danismith @@ -21,52 +21,123 @@ ms.custom: search.appverid: - MET150 - MOE150 -description: "Learn how to automatically invite members to become owners in an ownerless Microsoft 365 group or a team in Microsoft Teams." +description: Learn how to automatically invite members to become owners in an ownerless Microsoft 365 group or a team in Microsoft Teams. --- # Manage ownerless Microsoft 365 groups and teams -A team in Microsoft Teams or a Microsoft 365 group and its related services can become ownerless if an owner's account is deleted in Microsoft 365. Groups and teams require an owner to add or remove members and change group settings. +A team in Microsoft Teams or a Microsoft 365 group can become ownerless if an owner's account is deleted in Microsoft 365. Groups and teams require an owner to add or remove members and change group settings. -An Exchange Administrator or Groups Administrator can create a policy that automatically asks the most active members of an ownerless group or team if they'll accept ownership. When a member accepts the invitation to become an owner, the action is logged in the compliance portal audit log. Guests are never invited to be owners. +This article teaches you how to handle ownerless Microsoft 365 groups. + +## How the ownerless group policy works + +An Exchange administrator or Groups administrator can create a policy that automatically asks the members who are the most active in the group if they accept ownership. + +When a member accepts the invitation to become an owner, the action is logged in the compliance portal audit log. + +If there's no group activity, the policy asks random group members to accept ownership. + +## Requirements of the ownerless group policy + +To set up and manage the Microsoft 365 ownerless group policy, all the following requirements must be met: + +- **An eligible Microsoft 365 subscription** + - Eligible plans include Business Premium, Microsoft 365 Enterprise E3 and E5, Office 365 and Microsoft 365 Government G3 and G5, Microsoft 365 Education A3 and A5, and Frontline F1 and F3. + +- **A premium plan** + - All notification options in the ownerless groups policy require a premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of premium plans. + +## Limitations of the ownerless group policy + +Managing ownerless groups using this policy has a few limitations, which are explained in the following list: + +- **The ownerless group policy only applies to Microsoft 365 groups.** + - Not all SharePoint, Stream, and other apps' groups are Microsoft 365 groups. Viva Engage groups are Microsoft 365 groups if the tenant is in Native mode. + +- **You can't batch update the groups the policy targets.** + - You can only search for and add one Microsoft 365 group at a time to this policy. + +## Ownerless groups policy options When creating the policy, you can specify: -- If you want to limit who can be invited to be an owner by specifying a security group -- The sender address of the notifications -- The number of weeks that the notifications will be sent + +- If you want to limit who can be invited to be an owner by specifying a security group. +- The sender address of the notifications. +- The number of weeks that the notifications are sent. - Which groups or teams are part of the policy. A maximum of 50 groups can be selected. +- What the notification message says but not the language based on a recipient's country or region. -> [!Note] +> [!NOTE] > Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Entra ID P1 or P2 license for each Microsoft 365 group member in your organization. -To set an ownerless group or team policy +## Set up the ownerless group policy -1. In the admin center, go to **Show all** \> **Settings** \> **Org settings** and on the **Services** tab, select **Microsoft 365 Groups**. +To set an ownerless group or team policy, complete the following steps: -1. Select the **When there's no owner, email and ask active group members to become an owner** check box. +1. In the Microsoft 365 admin center, expand **Settings** and select **Org settings**. +1. On the [**Services**](https://go.microsoft.com/fwlink/p/?linkid=2053743) tab, select **Microsoft 365 Groups**. +1. Select the **When there's no owner, email and ask active group members to become an owner** checkbox. +1. If you want to keep the default configuration settings, select **Save**. -1. If you want to keep the default configuration settings, select **Save**, otherwise, select **Configure policy** and complete the following steps. +To customize the policy, complete the following steps: +1. On the **Microsoft 365 Groups** page, select **Configure policy**. 1. On the *Weekly notification options* page, specify who can receive ownership notifications. If you choose to allow or block certain members, then search for and add the security group that you want to use. + 1. Type the number of active members that you want to notify, and select the number of weeks to send the notification. The notification list is created during the first notification and doesn't change. + 1. Select **Next**. +1. On the *Who is this email coming from* page, select a sender for the email, and then select **Next**. + 1. Shared mailboxes aren't supported. The sender must be either a user mailbox or a group mailbox. +1. On the *Subject and message* page, customize the email and optionally include a **policy guideline URL**, and then select **Next**. +1. On the *Select which groups to target* page, select **Specific groups**, and choose the groups and teams that you want to include in this policy, or select **All groups**. +1. Select **Next**. +1. On the *Review and finish* page, confirm your settings and select **Finish**, and then select **Done**. -1. Type the number of active members that you want to notify and select the number of weeks to send the notification. (The notification list is created during the first notification and does not change.) Select **Next**. +## What happens after the policy is set up -1. On the *Who is this email coming from* page, select a sender for the email, and then select **Next**. Note that shared mailboxes are not supported. The sender must be either a user mailbox or a group mailbox. +Notifications are sent weekly starting within 24 hours of policy creation. Notifications and responses are tracked in the audit log. -1. On the *Subject and message* page, customize the email and optionally include a **policy guideline URL**, and then select **Next**. +If a user is a part of multiple ownerless groups, they can receive separate weekly notifications, one for each group they're an active member of. -1. On the *Select which groups to target* page, select **Specific groups** and choose the groups and teams that you want to include in this policy, or select **All groups**. +### What happens when someone accepts or declines ownership of a group -1. Select **Next**. +Up to two members per group can accept the invitation to become an owner. Once someone accepts ownership, the policy stops sending notifications to the group's members. + +If a member declines ownership, they stop receiving the weekly notifications. + +If a member doesn't accept or decline ownership, they keep receiving the weekly notifications for the number of weeks specified in the policy. + +### What happens if no members accept ownership + +After the end of the notification period specified in the policy, the policy stops sending notifications. In this scenario, the ownerless groups policy takes no further action and it's up to tenant admins to find and [assign an owner for each ownerless group](/admin/create-groups/add-or-remove-members-from-groups). + +## See which groups are ownerless + +Admins can see which Microsoft 365 groups remain ownerless by searching the [audit log](/purview/audit-search#get-started-with-search) in the Microsoft Purview portal. To search for ownerless groups, follow these steps: + +1. Sign in to the [Microsoft Purview portal](https://purview.microsoft.com/). +1. Select the **Audit** solution card. + 1. If the **Audit** solution card isn't displayed, select **View all solutions**, and then select **Audit** in the **Core** section. +1. On the **Search** page, in the **Activities - friendly names** field, select **Unattended ownerless group** from the dropdown list. +1. Select the **Search** button. + +## Common issues with the ownerless group policy -1. On the *Review and finish* page, confirm your settings and click **Finish**, and then select **Done**. +- **Exchange Online throttles policy notifications.** + - Because this policy sends notifications from one mailbox, the policy's notification emails could be throttled if there are too many ownerless groups in your organization. Exchange Online mailboxes are limited to 10,000 sent emails per day. -Notifications are sent weekly starting within 24 hours of policy creation. Recipients can't forward the notifications to others. Notifications and responses are tracked in the audit log. +- **The action buttons *Yes* and *No* aren't available in a forwarded notification email.** + - If a member forwards their notification email to a different member, the forward recipient can't accept or decline the invitation. -Up to two group members per group can accept the invitation to become an owner. If no group members accept, an administrator will have to [assign a group owner](/admin/create-groups/add-or-remove-members-from-groups). +- **Member can't see *Yes* and *No* in the notification email.** + - Notification emails should be opened in a separate window, not a preview pane. If the member views the notification in an email preview pane, they can't see the **Yes** and **No** options. + - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](/add-users/change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. -## Related topics +- **The policy for ownerless groups is configured, but group members don't receive notifications.** + - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/compliance/set-up-basic-audit#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. + - Members who don't have a user mailbox provisioned in Exchange Online don't receive notifications. -[Ownerless group FAQ](/exchange/troubleshoot/groups-and-distribution-lists/ownerless-group-policy) +## Related articles -[Search the audit log in the compliance portal](/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance) +- [Ownerless group FAQ](/exchange/troubleshoot/groups-and-distribution-lists/ownerless-group-policy) +- [Search the audit log in the compliance portal](/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance) From 068d530edc7c4599f5a80a0a38c1d5e045b91ba3 Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 16 Jan 2025 17:11:40 -0600 Subject: [PATCH 02/16] Update ownerless-groups-teams.md --- .../create-groups/ownerless-groups-teams.md | 44 +++++++------------ 1 file changed, 17 insertions(+), 27 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index f813d29109a..352cf22a037 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -28,7 +28,7 @@ description: Learn how to automatically invite members to become owners in an ow A team in Microsoft Teams or a Microsoft 365 group can become ownerless if an owner's account is deleted in Microsoft 365. Groups and teams require an owner to add or remove members and change group settings. -This article teaches you how to handle ownerless Microsoft 365 groups. +This article teaches you how to handle ownerless Microsoft 365 groups in the Microsoft 365 admin center. ## How the ownerless group policy works @@ -40,13 +40,15 @@ If there's no group activity, the policy asks random group members to accept own ## Requirements of the ownerless group policy -To set up and manage the Microsoft 365 ownerless group policy, all the following requirements must be met: +To set up and manage the Microsoft 365 ownerless group policy, **one** of the the following requirements must be met: - **An eligible Microsoft 365 subscription** - Eligible plans include Business Premium, Microsoft 365 Enterprise E3 and E5, Office 365 and Microsoft 365 Government G3 and G5, Microsoft 365 Education A3 and A5, and Frontline F1 and F3. -- **A premium plan** - - All notification options in the ownerless groups policy require a premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of premium plans. +or + +- **An Entra ID P1 or P2 premium plan** + - All notification options in the ownerless groups policy require an Entra ID premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of Entra ID premium plans. ## Limitations of the ownerless group policy @@ -58,48 +60,36 @@ Managing ownerless groups using this policy has a few limitations, which are exp - **You can't batch update the groups the policy targets.** - You can only search for and add one Microsoft 365 group at a time to this policy. -## Ownerless groups policy options - -When creating the policy, you can specify: - -- If you want to limit who can be invited to be an owner by specifying a security group. -- The sender address of the notifications. -- The number of weeks that the notifications are sent. -- Which groups or teams are part of the policy. A maximum of 50 groups can be selected. -- What the notification message says but not the language based on a recipient's country or region. - -> [!NOTE] -> Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Entra ID P1 or P2 license for each Microsoft 365 group member in your organization. - -## Set up the ownerless group policy - -To set an ownerless group or team policy, complete the following steps: +## Set up the ownerless group or team policy 1. In the Microsoft 365 admin center, expand **Settings** and select **Org settings**. 1. On the [**Services**](https://go.microsoft.com/fwlink/p/?linkid=2053743) tab, select **Microsoft 365 Groups**. 1. Select the **When there's no owner, email and ask active group members to become an owner** checkbox. 1. If you want to keep the default configuration settings, select **Save**. -To customize the policy, complete the following steps: +## Customize the ownerless group policy -1. On the **Microsoft 365 Groups** page, select **Configure policy**. +1. On the **Microsoft 365 Groups** pane, select **Configure policy**. 1. On the *Weekly notification options* page, specify who can receive ownership notifications. If you choose to allow or block certain members, then search for and add the security group that you want to use. - 1. Type the number of active members that you want to notify, and select the number of weeks to send the notification. The notification list is created during the first notification and doesn't change. - 1. Select **Next**. + 1. Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Entra ID P1 or P2 license for each Microsoft 365 group member in your organization. + 2. Type the number of active members that you want to notify, and select the number of weeks to send the notification. The notification list is created during the first notification and doesn't change. + 3. Select **Next**. 1. On the *Who is this email coming from* page, select a sender for the email, and then select **Next**. 1. Shared mailboxes aren't supported. The sender must be either a user mailbox or a group mailbox. 1. On the *Subject and message* page, customize the email and optionally include a **policy guideline URL**, and then select **Next**. + 1. You can't have the notification's language change based on the recipient's country or region. 1. On the *Select which groups to target* page, select **Specific groups**, and choose the groups and teams that you want to include in this policy, or select **All groups**. + 1. A maximum of 50 groups can be selected. 1. Select **Next**. 1. On the *Review and finish* page, confirm your settings and select **Finish**, and then select **Done**. -## What happens after the policy is set up +## After you set up the ownerless group policy Notifications are sent weekly starting within 24 hours of policy creation. Notifications and responses are tracked in the audit log. If a user is a part of multiple ownerless groups, they can receive separate weekly notifications, one for each group they're an active member of. -### What happens when someone accepts or declines ownership of a group +### When someone accepts or declines group ownership Up to two members per group can accept the invitation to become an owner. Once someone accepts ownership, the policy stops sending notifications to the group's members. @@ -107,7 +97,7 @@ If a member declines ownership, they stop receiving the weekly notifications. If a member doesn't accept or decline ownership, they keep receiving the weekly notifications for the number of weeks specified in the policy. -### What happens if no members accept ownership +### When no one accepts group ownership After the end of the notification period specified in the policy, the policy stops sending notifications. In this scenario, the ownerless groups policy takes no further action and it's up to tenant admins to find and [assign an owner for each ownerless group](/admin/create-groups/add-or-remove-members-from-groups). From 89cac161ede3f952003745de96aa674e66b005ca Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Fri, 17 Jan 2025 15:11:26 -0600 Subject: [PATCH 03/16] Update ownerless-groups-teams.md Updating related articles --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 352cf22a037..43af3a3896e 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -129,5 +129,6 @@ Admins can see which Microsoft 365 groups remain ownerless by searching the [a ## Related articles -- [Ownerless group FAQ](/exchange/troubleshoot/groups-and-distribution-lists/ownerless-group-policy) +- [Overview of Microsoft 365 Groups for administrators](office-365-groups.md). +- [Compare types of groups in Microsoft 365](compare-groups.md). - [Search the audit log in the compliance portal](/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance) From bbddbc82e80c45051878b8087cdd6a7807325c39 Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Fri, 17 Jan 2025 15:16:12 -0600 Subject: [PATCH 04/16] Update ownerless-groups-teams.md Updating license requirement --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 43af3a3896e..04efacdb2ac 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -47,8 +47,8 @@ To set up and manage the Microsoft 365 ownerless group policy, **one** of the th or -- **An Entra ID P1 or P2 premium plan** - - All notification options in the ownerless groups policy require an Entra ID premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of Entra ID premium plans. +- **An Azure P1 or P2 premium plan** + - All notification options in the ownerless groups policy require an Azure premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of Azure premium plans. ## Limitations of the ownerless group policy @@ -71,7 +71,7 @@ Managing ownerless groups using this policy has a few limitations, which are exp 1. On the **Microsoft 365 Groups** pane, select **Configure policy**. 1. On the *Weekly notification options* page, specify who can receive ownership notifications. If you choose to allow or block certain members, then search for and add the security group that you want to use. - 1. Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Entra ID P1 or P2 license for each Microsoft 365 group member in your organization. + 1. Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Azure P1 or P2 license for each Microsoft 365 group member in your organization. 2. Type the number of active members that you want to notify, and select the number of weeks to send the notification. The notification list is created during the first notification and doesn't change. 3. Select **Next**. 1. On the *Who is this email coming from* page, select a sender for the email, and then select **Next**. From 5b7e2d688f7a9e2b919223ba9a4d4435875fcbe1 Mon Sep 17 00:00:00 2001 From: e sung Date: Wed, 22 Jan 2025 19:59:10 -0800 Subject: [PATCH 05/16] specified version backups as part of total size --- microsoft-365/backup/backup-pricing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/backup/backup-pricing.md b/microsoft-365/backup/backup-pricing.md index 54be02ebb5f..959b32b2cea 100644 --- a/microsoft-365/backup/backup-pricing.md +++ b/microsoft-365/backup/backup-pricing.md @@ -26,7 +26,7 @@ The Microsoft 365 Backup service, offered through the Microsoft 365 admin center Microsoft 365 Backup charges you based on the size of the following content for 365 days from the time it's added to backup protection: -- Cumulative back up size of the mailboxes, SharePoint sites, and OneDrive accounts being protected. Size of OneDrive accounts and SharePoint sites are the size of the live OneDrive accounts and SharePoint sites as displayed in the live sites’ usage reports. Mailboxes are the size of the user's primary mailbox plus their online archives plus deleted items held for backup. +- Cumulative back up size of the mailboxes, SharePoint sites, and OneDrive accounts being protected. Size of OneDrive accounts and SharePoint sites are the size of the live OneDrive accounts and SharePoint sites as displayed in the live sites’ usage reports. Mailboxes are the size of the user's primary mailbox plus their online archives plus deleted/versioned items held for backup. - Deleted content in user’s Recycle Bin and second-stage Recycle Bin (also known as Site Collection Recycle Bin). From 41c76991ccb62cc5551cf23c6bc8e1c4c13615bc Mon Sep 17 00:00:00 2001 From: briannds <191177084+briannds@users.noreply.github.com> Date: Thu, 23 Jan 2025 09:44:36 -0500 Subject: [PATCH 06/16] Fixes to formatting issues --- copilot/release-notes.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/copilot/release-notes.md b/copilot/release-notes.md index c375032920c..927db8e7741 100644 --- a/copilot/release-notes.md +++ b/copilot/release-notes.md @@ -55,9 +55,9 @@ This is our preview version of Microsoft 365 Copilot release notes. We will use - **Listen to Copilot's responses with Read Aloud** [Windows, Mac] Hear Copilot’s replies in the chat pane, letting you stay hands-free while reviewing your content. Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. - +### SharePoint - **Copilot in SharePoint** [Web] - Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. + Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. ### Viva Amplify - **Microsoft 365 Copilot in Viva Amplify editor** [Web] The superpowers of Microsoft 365 Copilot integrates seamlessly into Viva Amplify, transforming content creation. Use Copilot in Amplify to auto-rewrite for suggestions, expand or condense text, and adjust tone for consistent, relevant messaging. Learn more. @@ -608,7 +608,8 @@ This is our preview version of Microsoft 365 Copilot release notes. We will use - **Create presentations using your organization's templates** [Windows, Web, iOS, Mac] Generate presentations that utilize your company's templates, ensuring consistency and alignment with your brand. Learn more. - **Edit your presentation in Copilot chat** [Windows, Web, iOS, Mac] - Add slides, add animations, or organize your presentation in Copilot chat, streamlining your editing process. Learn more. + Add slides, add animations, or organize your presentation in Copilot chat, streamlining your editing process. Learn more. + - **Get answers about your presentation** [Windows, Web, iOS, Mac] Ask questions about your existing PowerPoint presentation to quickly retrieve information and insights. - **Organize your presentation's flow easily** [Windows, Web, iOS, Mac] @@ -1024,12 +1025,11 @@ This is our preview version of Microsoft 365 Copilot release notes. We will use - **Updated meeting entity card in Copilot Chat** [Windows, Web] Check meeting details like RSVP status, date, and attachments without switching contexts in Copilot Chat. ### PowerPoint - Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. - +- **Generate summaries for longer presentations** [Windows, Web, Mac] Copilot now supports text summaries up to 40k words (around 150 slides), giving you richer information and more polished layouts. Learn more. ### SharePoint - Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. - Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content.Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. +- **Copilot in SharePoint** [Web] + Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. ### Viva Amplify - **Microsoft 365 Copilot in Viva Amplify editor** [Web] The superpowers of Microsoft 365 Copilot integrates seamlessly into Viva Amplify, transforming content creation. Use Copilot in Amplify to auto-rewrite for suggestions, expand or condense text, and adjust tone for consistent, relevant messaging. Learn more. From 0db6df4253c17b8c4efccc0d1af0c839712c6454 Mon Sep 17 00:00:00 2001 From: briannds <191177084+briannds@users.noreply.github.com> Date: Thu, 23 Jan 2025 10:02:40 -0500 Subject: [PATCH 07/16] Another fix --- copilot/release-notes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/copilot/release-notes.md b/copilot/release-notes.md index 927db8e7741..ef7f47c94ca 100644 --- a/copilot/release-notes.md +++ b/copilot/release-notes.md @@ -54,7 +54,6 @@ This is our preview version of Microsoft 365 Copilot release notes. We will use Copilot now supports text summaries up to 40k words (around 150 slides), giving you richer information and more polished layouts. Learn more. - **Listen to Copilot's responses with Read Aloud** [Windows, Mac] Hear Copilot’s replies in the chat pane, letting you stay hands-free while reviewing your content. - Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. ### SharePoint - **Copilot in SharePoint** [Web] Copilot in SharePoint combines the power of Large Language Models (LLMs), your data in the Microsoft Graph, and best practices to create engaging web content. Get assistance drafting your content when creating new pages. Adjust the tone, expand meeting bullets into structured text, or get help making your message more concise. All within our existing commitments to data security and privacy in the enterprise. Learn more. From 142c9cd5407b6628b48ecc66a9004fc77db7f46b Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 23 Jan 2025 10:23:08 -0600 Subject: [PATCH 08/16] Update ownerless-groups-teams.md Minor edits --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 04efacdb2ac..aa293b72ae8 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -40,13 +40,11 @@ If there's no group activity, the policy asks random group members to accept own ## Requirements of the ownerless group policy -To set up and manage the Microsoft 365 ownerless group policy, **one** of the the following requirements must be met: +To set up and manage the Microsoft 365 ownerless group policy, **one** of the following requirements must be met: - **An eligible Microsoft 365 subscription** - Eligible plans include Business Premium, Microsoft 365 Enterprise E3 and E5, Office 365 and Microsoft 365 Government G3 and G5, Microsoft 365 Education A3 and A5, and Frontline F1 and F3. -or - - **An Azure P1 or P2 premium plan** - All notification options in the ownerless groups policy require an Azure premium plan because a security group is used to specify which group members receive ownership notifications. Security groups are a feature of Azure premium plans. From f5bc5664b553a69ff88b081c34e8c06131a41bdf Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 23 Jan 2025 11:30:28 -0500 Subject: [PATCH 09/16] Fix broken links in ownerless groups documentation --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index aa293b72ae8..8d2b0bb2567 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -119,10 +119,10 @@ Admins can see which Microsoft 365 groups remain ownerless by searching the [a - **Member can't see *Yes* and *No* in the notification email.** - Notification emails should be opened in a separate window, not a preview pane. If the member views the notification in an email preview pane, they can't see the **Yes** and **No** options. - - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](/add-users/change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. + - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../add-users/change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. - **The policy for ownerless groups is configured, but group members don't receive notifications.** - - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/compliance/set-up-basic-audit#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. + - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/purview/audit-get-started#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. - Members who don't have a user mailbox provisioned in Exchange Online don't receive notifications. ## Related articles From 4bbc44ee2f2fa054962306ab7999c588b261986d Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 23 Jan 2025 11:36:53 -0500 Subject: [PATCH 10/16] Fix broken link in ownerless groups documentation --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 8d2b0bb2567..b20b3b68c17 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -119,7 +119,7 @@ Admins can see which Microsoft 365 groups remain ownerless by searching the [a - **Member can't see *Yes* and *No* in the notification email.** - Notification emails should be opened in a separate window, not a preview pane. If the member views the notification in an email preview pane, they can't see the **Yes** and **No** options. - - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../add-users/change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. + - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../../change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. - **The policy for ownerless groups is configured, but group members don't receive notifications.** - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/purview/audit-get-started#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. From 838cfc8ee8454a82c3503762c7623041f332d720 Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 23 Jan 2025 11:39:46 -0500 Subject: [PATCH 11/16] Fix broken link in ownerless groups documentation --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index b20b3b68c17..8da9f50102d 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -119,7 +119,7 @@ Admins can see which Microsoft 365 groups remain ownerless by searching the [a - **Member can't see *Yes* and *No* in the notification email.** - Notification emails should be opened in a separate window, not a preview pane. If the member views the notification in an email preview pane, they can't see the **Yes** and **No** options. - - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../../change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. + - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../../change-a-user-name-and-email-address.md). If they don't match, the recipient can't see the **Yes** and **No** options. - **The policy for ownerless groups is configured, but group members don't receive notifications.** - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/purview/audit-get-started#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. From 2902b0481e170cc06bedb33ee7a61235cbedee1e Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Thu, 23 Jan 2025 11:43:18 -0500 Subject: [PATCH 12/16] Update link to change user name and email --- microsoft-365/admin/create-groups/ownerless-groups-teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 8da9f50102d..8195ea1f214 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -119,7 +119,7 @@ Admins can see which Microsoft 365 groups remain ownerless by searching the [a - **Member can't see *Yes* and *No* in the notification email.** - Notification emails should be opened in a separate window, not a preview pane. If the member views the notification in an email preview pane, they can't see the **Yes** and **No** options. - - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](../../change-a-user-name-and-email-address.md). If they don't match, the recipient can't see the **Yes** and **No** options. + - Make sure that the user principal name (UPN) and primary email address of the sender are the same. For information about how to update the UPN or primary email address of a user, see [Change a user name and email address](/microsoft-365/admin/add-users/change-a-user-name-and-email-address). If they don't match, the recipient can't see the **Yes** and **No** options. - **The policy for ownerless groups is configured, but group members don't receive notifications.** - This issue occurs if the specified sender in the policy doesn't have a user or group mailbox provisioned in Exchange Online. If the sender has a user or group mailbox, check the [audit log](/purview/audit-get-started#step-3-search-the-audit-log) in the [Microsoft Purview portal](https://go.microsoft.com/fwlink/p/?linkid=2077149) to trace whether email notifications were sent. From 36cfb49548f1b54b63e1b24b43a0b782d99fb456 Mon Sep 17 00:00:00 2001 From: Kweku Ako-Adjei <35539435+kwekuako@users.noreply.github.com> Date: Thu, 23 Jan 2025 09:00:34 -0800 Subject: [PATCH 13/16] Update message-center.md --- microsoft-365/admin/manage/message-center.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/microsoft-365/admin/manage/message-center.md b/microsoft-365/admin/manage/message-center.md index d63f89629a1..1ea631c338c 100644 --- a/microsoft-365/admin/manage/message-center.md +++ b/microsoft-365/admin/manage/message-center.md @@ -133,16 +133,12 @@ Major updates can be reviewed by selecting the **Major update** from the **Tags* Major updates are communicated at least 30 days in advance when an action is required and might include: -- Changes to daily productivity such as inbox, meetings, delegations, sharing, and access -- Changes to themes, web parts, and other components that may affect customized features -- Increases or decreases to visible capacity such as storage, number of rules, items, or durations -- Changes to product branding that may: - - Cause end user confusion, - - Result in changes to help desk processes and reference material, or - - Change a URL -- A new service or application -- Changes requiring an admin action (exclusive of prevent or fix issues) -- Changes to where your data is stored +- User impacting changes to daily productivity such as changing a user’s inbox, meetings, delegations, sharing and access that may result in help desk calls, or organizational conformance concerns. +- Changes to the themes, web parts, deployed Copilot agents and other components that may impact customer customizations. +- Increases or decreases to visible capacity such as storage, number of rules, Copilot agents and prompts, items, or durations. +- Rebranding that may cause end-user confusion or result in help desk changes, collateral changes, or URL changes if the new URL is not *.cloud.microsoft +- A new service or application deployed with default settings turned on. +- Changes to where data is stored or accessed. ### Preferences From 4dbde9420d43db9e1f4be98615c0afac8b40ed38 Mon Sep 17 00:00:00 2001 From: Padma Jayaraman Date: Thu, 23 Jan 2025 22:41:27 +0530 Subject: [PATCH 14/16] Corrected the formatting for the screen elements --- .../admin/create-groups/ownerless-groups-teams.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/microsoft-365/admin/create-groups/ownerless-groups-teams.md b/microsoft-365/admin/create-groups/ownerless-groups-teams.md index 8195ea1f214..87a3cfb9300 100644 --- a/microsoft-365/admin/create-groups/ownerless-groups-teams.md +++ b/microsoft-365/admin/create-groups/ownerless-groups-teams.md @@ -68,18 +68,18 @@ Managing ownerless groups using this policy has a few limitations, which are exp ## Customize the ownerless group policy 1. On the **Microsoft 365 Groups** pane, select **Configure policy**. -1. On the *Weekly notification options* page, specify who can receive ownership notifications. If you choose to allow or block certain members, then search for and add the security group that you want to use. +1. On the **Weekly notification options** page, specify who can receive ownership notifications. If you choose to allow or block certain members, then search for and add the security group that you want to use. 1. Using a security group to limit who can be invited to be an owner requires that you possess but not necessarily assign a Microsoft Azure P1 or P2 license for each Microsoft 365 group member in your organization. 2. Type the number of active members that you want to notify, and select the number of weeks to send the notification. The notification list is created during the first notification and doesn't change. 3. Select **Next**. -1. On the *Who is this email coming from* page, select a sender for the email, and then select **Next**. +1. On the **Who is this email coming from** page, select a sender for the email, and then select **Next**. 1. Shared mailboxes aren't supported. The sender must be either a user mailbox or a group mailbox. -1. On the *Subject and message* page, customize the email and optionally include a **policy guideline URL**, and then select **Next**. +1. On the **Subject and message** page, customize the email and optionally include a **policy guideline URL**, and then select **Next**. 1. You can't have the notification's language change based on the recipient's country or region. -1. On the *Select which groups to target* page, select **Specific groups**, and choose the groups and teams that you want to include in this policy, or select **All groups**. +1. On the **Select which groups to target** page, select **Specific groups**, and choose the groups and teams that you want to include in this policy, or select **All groups**. 1. A maximum of 50 groups can be selected. 1. Select **Next**. -1. On the *Review and finish* page, confirm your settings and select **Finish**, and then select **Done**. +1. On the **Review and finish** page, confirm your settings and select **Finish**, and then select **Done**. ## After you set up the ownerless group policy From 1c87930e7cd92b1e7befbc0c064f359406df3ba4 Mon Sep 17 00:00:00 2001 From: Ruchika Mittal Date: Thu, 23 Jan 2025 23:11:13 +0530 Subject: [PATCH 15/16] acro fix --- microsoft-365/admin/manage/message-center.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-365/admin/manage/message-center.md b/microsoft-365/admin/manage/message-center.md index 1ea631c338c..de810d58cdb 100644 --- a/microsoft-365/admin/manage/message-center.md +++ b/microsoft-365/admin/manage/message-center.md @@ -211,7 +211,7 @@ Here's a quick overview of the information in each column. |Check mark|Selecting the check mark in the column heading row selects all messages currently displayed. Selecting the check mark next to one or more messages lets you take action on those messages.| |Message title|Message titles are brief descriptions of upcoming changes. If the full title doesn't display, hover your cursor over it and the entire title will appear in a pop-up box.| |Service|Icons indicate the application to which the message applies.| -|More options|More options lets you dismiss a message, mark it as read or unread, or share it with another admin. To restore an archived message, select the **Archive** tab, select the check mark next to the message, and select **Restore**.| +|More options|More options let you dismiss a message, mark it as read or unread, or share it with another admin. To restore an archived message, select the **Archive** tab, select the check mark next to the message, and select **Restore**.| |Tags| You can choose tags from the Tag drop-down to filter messages.

**Data Privacy**: Data privacy notification (limited to global administrator and Message center Privacy reader roles).

**Major update**: Changes communicated at least 30 days in advance ([Major updates](#major-updates)).

**Retirement**: Retirement of a service or feature.

**New feature**: New feature or service.

**Feature update**: Update to an existing feature.

**Admin impact**: When the change clearly impacts the admin in the following ways - UI change, workflow change, control available and Specific/Potential Action.

**User impact**: When the change to the service clearly impacts the user - UI Change and workflow change.

**Updated message**: When a message is updated.| |Category| This is not shown by default, but can be specified in the **Choose columns** panel. Messages are identified by one of the following three categories:

**Prevent or fix issues**: Informs you of known issues affecting your organization and may require that you take action to avoid disruptions in service. Prevent or fix issues are different than Service health messages because they prompt you to be proactive to avoid issues.

**Plan for change**: Informs you of changes to Microsoft 365 that may require you to act to avoid disruptions in service. For example, we let you know about changes to system requirements or about features that are being removed. We try to provide at least 30 days' notice of any change that requires an admin to act to keep the service running normally.

**Stay informed**: Tells you about new or updated features we are turning on in your organization. announced first in the [Microsoft 365 Roadmap](https://go.microsoft.com/fwlink/?linkid=2070821).

May also let you know about planned maintenance in accordance with our Service Level Agreement. Planned maintenance may result in down time, where you or your users can't access Microsoft 365, a specific feature, or a service such as email or OneDrive for Business.| |Act by|We'll only have dates here if we're making a change that requires you to take an action by a certain deadline. Since we rarely use the **Act by** column, if you see something here, you should pay extra attention to it.| @@ -235,7 +235,7 @@ Here's a quick overview of the information in each column. In the Message center, you can select a message to see details. -If a Message Center post is not relevant for your organization, please provide us feedback using the options demonstrated in the image below. After you click thumbs up/down on the MC post, select "this change isn't relevant to my org." +If a Message Center post is not relevant for your organization, please provide us with feedback using the options demonstrated in the image below. After you click thumbs up/down on the MC post, select "this change isn't relevant to my org." :::image type="content" source="../../media/message-center-feedbacksection.jpg" alt-text="Message center view of feedback section."::: From a243f5905c40fa52d4c7e305f37c806732e055c1 Mon Sep 17 00:00:00 2001 From: Ruchika Mittal Date: Thu, 23 Jan 2025 23:27:41 +0530 Subject: [PATCH 16/16] acro fix --- microsoft-365/backup/backup-pricing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-365/backup/backup-pricing.md b/microsoft-365/backup/backup-pricing.md index 959b32b2cea..6d44844431e 100644 --- a/microsoft-365/backup/backup-pricing.md +++ b/microsoft-365/backup/backup-pricing.md @@ -61,7 +61,7 @@ To use the Microsoft 365 Backup pricing calculator, you need to perform the foll 1. Download the latest version of the [Microsoft 365 Backup pricing calculator tool](https://aka.ms/M365BackupCalculator). -2. Review your [Microsoft 365 usage reports](https://admin.microsoft.com/Adminportal/Home#/reportsUsage) to get historical information about your current usage. Heuristics from the usage reports will be used to populate the inputs (orange boxes) in the pricing calculator tool. Content in the OneDrive and SharePoint recycle bins and data in archive maiboxes won't be reflected in these reports, but do affect the backup costs as previously described. +2. Review your [Microsoft 365 usage reports](https://admin.microsoft.com/Adminportal/Home#/reportsUsage) to get historical information about your current usage. Heuristics from the usage reports will be used to populate the inputs (orange boxes) in the pricing calculator tool. Content in the OneDrive and SharePoint recycle bins and data in archive mailboxes won't be reflected in these reports, but do affect the backup costs as previously described. 3. Open the Excel spreadsheet and select the **High-Level Estimates** worksheet. This sheet produces the simplest default model based on linear data growth assumptions.