+When you uncheck the 'Allow users to be asked whether they want to pin it' option, Microsoft Copilot will no longer appear in the App Launcher.

+1. Select the **Microsoft 365 Copilot** page.

+- Assign targeting via Microsoft Entra user groups and advanced targeting options

+- **Message recipients** anyone in your organization who might receive messages from your authors must have access to the Microsoft products to which the messages are configured to be delivered. (End users aren't required to have any Microsoft Entra roles to receive organizational messages.)

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

+If you have the Organizational Messages Writer Microsoft Entra role as described above, you can edit or otherwise complete a saved ΓÇÿdraftΓÇÖ message in your tenant. To do so:

+If you have the Organizational Messages Approver Microsoft Entra role as described above, 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 above, you can overcome a rejection from the approvers in your tenant. To do so:

+Users with the Organizational Messages Writer Microsoft Entra role described previously will have access to the **Create a message** button and capability in the centralized experience. Selecting this button invokes the wizard, which includes these primary creation steps:

+ Reach out to a Global admin and ask them to assign you Organizational Messages Writer or Organizational Message Approver Microsoft Entra role to you following these steps:

+### How does localization work in Organizational messages?

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

+- en-US

+- de-DE

+- es

+- fr-FR

+- it-IT

+- ja-JP

+- ko-KR

+- nl-NL

+- pl-PL

+- pt-BR

+- pt-PT

+- ru-RU

+- tr-TR

+- zh-Hans

+- zh-Hant

+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 will qualify to receive the message A.

+**For customized messages**, your message will only be delivered in the language in which it was created within the Microsoft 365 admin center.

+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 will qualify to receive the message B.

+The operational hierarchy coupled with this metadata enables frontline apps and experiences, like [targeted announcements in Viva Connections](/viva/connections/announcements-viva-connections), and numerous frontline capabilities, like task publishing, in the future. Start setting up your operational hierarchy today to get the full value of these upcoming features as they're released.

+| ParentName | Yes | The name of the parent node. The value you specify here must match the value in the **DisplayName** field of the parent node exactly. If you want to add more than one parent node, separate each parent node name with a semicolon (;). You can add up to 25 parent nodes, and each parent node name can be up to 2,500 characters long. A node can have multiple parent nodes only if the parent nodes are root nodes. <br><br>**IMPORTANT** Be careful not to create a loop where a parent higher up in the hierarchy references a child node lower in the hierarchy. This structure isn't supported. |

+## Related articles

+- [Use announcements in Viva Connections](/viva/connections/announcements-viva-connections)

+Setting up targeted communications in Microsoft Teams enables you to deliver personalized communications experiences, such as [automatic tags](#automatic-tags) and [targeted announcements in Viva Connections](#targeted-announcements-in-viva-connections), to your frontline teams.

+Streamline and simplify communications for your frontline. After you map your attributes, your frontline teams can use targeted communication features, like automatic tags in Teams channel conversations and targeted announcements in Viva Connections, and additional frontline capabilities that are coming soon.

+- To use [targeted announcements in Viva Connections](#targeted-announcements-in-viva-connections), your frontline teams must be created through the [deploy frontline dynamic teams](deploy-dynamic-teams-at-scale.md) experience and you must define a [frontline operational hierarchy](deploy-frontline-operational-hierarchy.md) in the Teams admin center.

+- To use [automatic tags](#automatic-tags), tags must be turned on for your organization. In the Teams admin center, go to **Teams** > **Teams settings**. Under **Tagging**, check that the **Who can manage tags** setting is set to an option other than **Not enabled**. [Learn more about how to turn on tags for your organization](/microsoftteams/manage-tags).

+## Targeted announcements in Viva Connections

+Announcements allow you to create and share targeted, time-sensitive messages in the Viva Connections app.

+- On Teams mobile, employees get a notification on the lock screen of their device alerting them of a new announcement.

+- In the Viva Connections mobile experience, the announcement appears at the top of the dashboard.

+Frontline managers can target announcements to specific groups of workers based on their location, department, and job title. When drafting an announcement, they can filter the audience by choosing location, department, and job title properties, which are automatically created based on your mapped attribute values.

+To learn more, see [Use announcements in Viva Connections](/viva/connections/announcements-viva-connections).

+- [Use announcements in Viva Connections](/viva/connections/announcements-viva-connections)

+3. From the **OS** filter, select an operating system or platform.

+ You can filter the results to see **Settings that differ**, **Settings that match**, or **Configured settings**.

+## Configure policy settings

+3. From the list of policies, select the policy that you want to configure.

+4. In the policy details pane, select **View this policy in Microsoft Intune admin center**.

+5. In the Microsoft Intune admin center, configure the policy settings as needed.

+[Overview of using Microsoft 365 Lighthouse baselines to deploy standard tenant configurations](m365-lighthouse-deploy-standard-tenant-configurations-overview.md) (article)

+- Review regressions such as tasks that change from a **Compliant** or **Dismissed** status to a status of **Not compliant** or **Not licensed**.

+2. On the **Deployment insights** page, review the following areas to gather insights on customer tenants' deployment progress.

+|Tenant progress | Provides a deployment progress summary across all tenants. You can hover over the graph to see the number of tenants with deployment plans that are **Complete** and **Not complete**. Tenants for which all assigned tasks are **Compliant** or **Dismissed** are considered **Complete**. Tenants for which one or more assigned tasks are **Not compliant** or **Not licensed** are considered **Not complete**. |

+|User progress | Provides a user-deployment progress summary for all users. You can hover over the graph to see the exact number of users that are **Complete** and **Not complete**. Users for whom all assigned tasks are **Compliant**, **Dismissed**, or **Not targeted** are considered **Complete**. Users for whom one or more assigned tasks is **Not compliant** or **Not licensed** are considered **Not complete**. |

+|Tenants tab | Provides detailed deployment progress for each tenant. You can use various data points from the table to determine the appropriate action. For example, the **Not licensed tasks** column indicates the number of tasks for which the tenant is not licensed. To resolve the issue, you can add a license or exclude the user from the task. The **Regressed tasks** column indicates that a task status changed from a **Compliant** or **Dismissed** state. You can go to the specific tenant deployment plan and take the appropriate action. |

+For additional solutions for common deployment issues, see the [Deploying baselines section in Microsoft 365 Lighthouse frequently asked questions (FAQs)](m365-lighthouse-faq.yml#deploying-baselines).

+2. On the **Tenants** tab, look for tenants that have a number other than **0** in the **Regressed tasks** column.

+3. Select the desired tenant to open the tenant details page and view the regressed tasks.

+4. To see the tenant's deployment plan, select **View tenant deployment plan**.

+5. From the **Deployment plan** tab, select the regressed task from the list to open the task details pane.

+2. On the **Tenants** tab, select a tenant that has a number other than **0** in the **Dismissed tasks** column to open the tenant details pane.

+4. From the list of dismissed tasks, review the reason and justification for each task to determine if the dismissal is still valid.

+5. If no longer valid, select the dismissed task from the list, and then select **Reinstate**.

+2. On the **Tenants** tab, select a tenant that has a number other than **0** in the **Excluded users** column to open the tenant details pane.

+4. From the list of tasks with excluded users, expand each task and determine if the listed user should still be excluded.

+6. From the **Deployment plan** tab, select the applicable deployment task from the list to open the task details pane.

+7. Select **Deploy**.

+8. On the **Review deployment task** page, remove the user from the **Exclude users** box, and then select **Next**.

+9. On the **Review tenant configurations** page, review the configurations, and then select **Next**.

+10. On the **Confirm configuration** page, review the configuration settings, and then select **Deploy**.

+[Microsoft 365 Lighthouse frequently asked questions (FAQs)](m365-lighthouse-faq.yml) (article)

+Microsoft 365 Lighthouse lets you change or reset user passwords. You can reset the password for one or more users or risky users across the same or different tenants.

+## Reset a password for one or more users

+1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Users** > **Account management**.

+2. On the **Search users** tab, enter all or part of the user's name in the search box and press **Enter**.

+3. From the search results list, select the checkbox next to one or more users in the list, and then select **Reset password**.

+4. In the **Reset password** pane, select **Autogenerate password** or **Let me create a password**. If you choose to create a password, enter a password in the **Password** box (the password will be the same for all selected users).

+6. If you want the users to change their password after first sign-in, select **Require these users to change their password when they first sign in**.

+7. Select **Reset password**.

+## Reset a password for one or more risky users

+2. On the **Risky users** page, select the checkbox next to one or more risky users in the list, and then select **Reset password**.

+4. In the **Reset password** pane, select **Autogenerate password** or **Let me create a password**. If you choose to create a password, enter a password in the **Password** box (the password will be the same for all selected users).

+5. If you want the users to change their password after first sign-in, select **Require these users to change their password when they first sign in**.