+- [Watch: Oversharing Control at Enterprise Scale](https://www.youtube.com/watch?v=F1ARVMTBAak)

+To learn more, watch [Oversharing Control at Enterprise Scale](https://www.youtube.com/watch?v=F1ARVMTBAak) (opens YouTube's website).

+- [Watch: Oversharing Control at Enterprise Scale](https://www.youtube.com/watch?v=F1ARVMTBAak)

+|[Microsoft Copilot usage report](microsoft-copilot-usage.md)|Yes|N/A²|N/A²|N/A²|N/A²|

+> As of November 19, 2024, Organizational Messages in the Microsoft 365 admin center is now in general availability.

+- Use or edit premade template messages from Microsoft

+- Send messages to Windows 10/11 and Microsoft 365 app locations, such as Windows Spotlight and Teams teaching popover (or coachmark)

+- Configure delivery schedules and parameters for messages, including via urgent messages configuration

+- Assign targeting via Microsoft Entra user groups and advanced targeting options, such as [Group Level Aggregate-based targeting](/microsoft-365/admin/adoption/group-level-aggregates)

+- Manage messages created in Microsoft 365 admin center and other portals, including [Usage reports](/microsoft-365/admin/activity-reports/microsoft-365-copilot-organizational-messages)

+> During our preview period, Organizational messages preview experiences were not restricted based on the licenses held by participating tenants, authors, approvers, or message recipients. However, now that the product is in general availability, some organizational messages experiences are restricted to particular Microsoft licenses. To learn more, see [Premium features](#premium-features).

+1. **Manage** ΓÇô Where you and your team can see most of your organizational messages created in various portals, including Usage reports and Copilot advanced deployment guide within the Microsoft 365 admin center. Your team can also execute various functions on each message, view details, and conduct approval flows in the 'Manage' area.

+2. **Create a message** ΓÇô The wizard where anyone with the above-described Organizational Messages Writer Microsoft Entra role can go to create either fully customized or templatized messages.

+3. **Review activity** ΓÇô Where your admins can go to see the performance activity of messages that are or have been delivering to your users.

+You can review and control the messages from anyone in their organization using the main landing experience. Operations that admins can affect within the 'Manage' experience include:

+If you have the Organizational Messages Approver Microsoft Entra role as described previously, you can review and approve or reject messages from your colleagues that are in the ΓÇÿpending approvalΓÇÖ state. To approve or reject a ΓÇÿpending approvalΓÇÖ message:

+If you have the Organizational Messages Writer Microsoft Entra role as described previously, you can overcome a rejection from the approvers in your tenant. To do so:

+>

+> [!NOTE]

+> To ensure tenant-based targeting, the organizational messages system may require up to 24-48 hours to establish any tenant that has not scheduled a message within the last 30 days.

+> [!NOTE]

+> The ability to create fully customized messages is enabled if your organization has at least one Microsoft license as described in the [Premium features](#premium-features) section.

+### How to enable targeting by Companies, Departments, Locations

+The advanced targeting options of ΓÇ£CompaniesΓÇ¥, ΓÇ£DepartmentsΓÇ¥, ΓÇ£LocationsΓÇ¥ in the **Recipients** step of the message creation flow are made possible by the group-level aggregates settings associated with Adoption Score. To learn more, see [Group Level Aggregates in Adoption Score](/microsoft-365/admin/adoption/group-level-aggregates).

+This advanced targeting in organizational messages can be enabled using the following:

+1. Go to **Settings** > **Org settings** within the Microsoft 365 admin center.

+2. Select **Adoption Score**.

+3. Under **Group data filtering**, select ΓÇ£Turn on group-level insightsΓÇ¥ and then ΓÇ£SaveΓÇ¥.

+4. Within **Adoption Score**, select the ΓÇ£Manage group-level filteringΓÇ¥ button.

+5. Select the ΓÇ£Organizational attributesΓÇ¥ checkbox and then the ΓÇ£Turn on selected filtersΓÇ¥ button.

+> [!NOTE]

+> The ability to use advanced targeting options is enabled if your organization has at least one Microsoft license as described in the [Premium features](#premium-features) section.

+3. You're immediately placed within the creation wizard with relevant elements from the previous message copied over.

+>

+> - Once you select ΓÇÿSend for approvalΓÇÖ at the end of a fully customized message creation flow, anyone in your tenant that has the Organizational Messages Approver Microsoft Entra role described previously will be able to review and approve/reject your message.

+### Urgent delivery

+For some time-sensitive communications, admins and other communicators might need to get a message out fast. For example, when an event is occurring on a corporate campus or a service outage has begun, admins might need to quickly broadcast such events to some employees so they can be prepared. To support communications in such events, admins in Microsoft 365 admin center will be able to select the ΓÇÿUrgent messagesΓÇÖ button in the ΓÇ£Top ActionsΓÇ¥ section.

+The message creation experience for an urgent message is similar to the flow for creating other messages with these exceptions:

+- The only locations available are Windows 10/11 Taskbar and Notifications area.

+- Only Microsoft Entra (formerly Azure Active Directory) group targeting can be used.

+- No Start/End dates nor frequency configurations are available as urgent messages are sent once as soon as possible.

+## Premium features

+Starting with general availability, organizational messages will also introduce the concept of ΓÇÿpremiumΓÇÖ features. These experiences are ones within the Organizational messages Microsoft 365 admin center which have tenant and end user requirements as follows:

+### Tenant - accessing premium features when creating messages

+Premium features will be accessible to admins within Organizational messages in Microsoft 365 admin center when their tenant has one of the following:

+1. -1+ Microsoft 365 E3-E5 licenses

+1. -1+ Office 365 E3-E5 licenses

+1. -1+ Windows 365 E3-E5 licenses

+### End user ΓÇô receiving messages with premium features

+End users within a tenant are eligible to receive messages created using premium features when these end users personally have one of the following:

+- Microsoft 365 E3-E5 license

+- Office 365 E3-E5 license

+- Windows 365 E3-E5 license

+### Current premium features

+For general availability, the premium features in Organizational messages in Microsoft 365 admin center are the following:

+1. Fully customized message creation

+> [!NOTE]

+> In general availability, message authors whose tenant satisfies premium feature requirements will be able to Edit a templatized message within the message creation flow.

+2. Advanced targeting ΓÇô group level aggregates (Department, Location, Company)

+> This policy is required for devices running [Windows](https://support.microsoft.com/topic/november-29-2022-kb5020044-os-build-22621-900-preview-43f0bdf9-0b75-4110-bab3-3bd2433d84b3), [version 22H2](https://support.microsoft.com/topic/november-29-2022-kb5020044-os-build-22621-900-preview-43f0bdf9-0b75-4110-bab3-3bd2433d84b3), [build 10.0.22621.900](https://support.microsoft.com/topic/november-29-2022-kb5020044-os-build-22621-900-preview-43f0bdf9-0b75-4110-bab3-3bd2433d84b3) and later. If you don't enable this policy, these devices can't receive organizational messages.

+> If you use the Windows MDM security baseline, you will need to change the required policies to **Not configured**. These policies control organizational messages configured by your team as well as other messages coming directly from Microsoft. To continue blocking messages coming directly from Microsoft as defined in the Windows MDM security baseline, configure the Microsoft messages policy found in the Organizational messages settings experience within the admin center.

+1. In configuration settings, ensure the following are deselected:

+For non-urgent messages, after your message has been scheduled by the Organizational Messages platform (for example, after approval from your Organizational Messages approvers is acquired as needed), at the earliest, it will take a few hours before the message will be eligible to be delivered to end user devices. For example, if you set the Start Date to be now/today, you should expect a few hours before any end user devices in your testing tenant receive the message payload.

+Further, Windows buffers messages on a set period for each of the channels. (In other words, this experience is delivered on a ΓÇÿpullΓÇÖ model.) So, expect that your message might take 24 or more hours for targeted end users in your tenant to receive and render the message as their devices might be configured to request content at different times.

+Once your message has been actively delivering for over 24 hours, you can return to the 'Manage' experience to review the latest delivery data for your message.

+For urgent messages, after your message has been scheduled by the Organizational Messages platform (for example, after approval from your Organizational Messages approvers is acquired as needed), the platform will try to send the message as soon as possible. However, as noted above, this is a best-effort mechanism subject to various conditions, with no guaranteed delivery times.

+The MDM policies listed under [Setting tenant policies](#setting-tenant-policies) control whether the service delivering the messages is able to access each location where organizational messages could be delivered. Previously, the CSPs only affected consumer scenarios and controlled whether Microsoft messaging can be delivered, however, since weΓÇÖre using the same service, the policies affect admin-created messages as well.

+1. Run *ms-settings:workplace*.

+3. **Failed** ΓÇô message was not able to be properly registered by the organizational messages services for various reasons. These messages need to be copied to retry the process.

+4. **Canceled** ΓÇô message was explicitly stopped by your tenant admin. This might have been during delivery of the message or prior (that is, in Scheduled state).

+**For premade messages**, your message is delivered to end users who have their related product language set to one of the following:

+For example, if the Organizational Messages Writer (admin) selects message A to be sent to their end users, then any end users with their product language set to one of the above languages qualify to receive the message A.

+For example, if the Organizational Messages Writer (admin) has their Microsoft 365 admin center product language set to French when they create their message B from scratch, end users with related product language set to English will not receive the message B. However, end users with French set as their related product language qualifies to receive the message B.

+### Does Organizational Messages support government environments, such as GCC, GCCH, etc.?

+No, not at this time.

+### Our team previously authored messages for the Windows Get Started location within the Organizational messages experience in Intune/Microsoft Endpoint Manager ΓÇô can we still do that in this experience within Microsoft 365 admin center?

+Any Get Started messages that you created in the Organizational messages experience within Intune/Microsoft Endpoint Manager that have not completed can be viewed within the Microsoft 365 admin center experience. However, new Get Started message creation is not yet supported at this time.

+### Are there any premade messages available for the Windows Spotlight location?

+No, not at this time.

+### Only Windows 11 deliveries were supported in the public preview ΓÇô is that still the case?

+Based on customer feedback, organizational messages now deliver to both Windows 10 and Windows 11 locations for the Notifications area, Taskbar, and Windows Spotlight.

+### My tenant only wants our end users to see messages from us, not Microsoft; how can we do that?

+After your admins enable all of the policies described in the previous section on [Setting Tenant Policies](#setting-tenant-policies), you can then go to the ΓÇÿSettingsΓÇÖ feature within the Organizational messages in Microsoft 365 admin center portal (top right corner of the landing page), deselect the option ΓÇ£Allow Microsoft messages to display,ΓÇ¥ and select ΓÇÿSaveΓÇÖ. This ensures Organizational messages platform sends only your teamΓÇÖs messages to Windows surfaces, like Taskbar.

+### If my organization only has an Office 365 E3 or E5 license, should I expect to be able to create fully customized messages on Windows locations, like Notifications area or Taskbar? Likewise, if my organization only has a Windows E3 or E5 license, should I expect to be able to create fully customized messages on the Teams location?

+No, the organizational messages creation flow will automatically disable authoring experiences that your tenant can't access based on the license requirements listed in the [Premium features](#premium-features) section. However, your organization may be able to create premade messages without such E3 or E5 licenses. For example, your team will not be able to create a fully customized message on Windows locations if your organization does not have at least a Windows E3 or E5 license or a Microsoft 365 E3 or E5 license. Similarly, your team won't be able to create a fully customized message on the Teams location if your organization doesn't have at least an Office 365 E3 or E5 license or a Microsoft 365 E3 or E5 license.

+An applied model processes all files and folder content uploaded to the document library after it's applied. You can also do the following steps to run the model on files and folder content that already exist in the document library prior to the model being applied.

+> [!NOTE]

+> To see custom Syntex commands like **Classify and extract** when you add a document library web part to a SharePoint site page, you must have a Syntex subscription.

+SharePoint eSignature is currently available in the US, UK, and Canada. It will be available in the EU and Australia Pacific by November 2024, and globally in 2025. Furthermore, the use of other eSignature providers as an integration with the SharePoint eSignature platform is available globally.

+- Support for Adobe Acrobat sign and Docusign is now available globally