merge
@ -1082,7 +1082,7 @@
|
||||
},
|
||||
{
|
||||
"source_path": "windows/configuration/shell-launcher/wedl-assignedaccess.md",
|
||||
"redirect_url": "/windows/configuration/shell-launcher/wedl-assignedaccess",
|
||||
"redirect_url": "/windows/configuration/assigned-access/wedl-assignedaccess",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
|
@ -90,7 +90,7 @@ A configuration file can contain one or more profiles. Each profile is identifie
|
||||
|
||||
A profile can be one of two types:
|
||||
|
||||
- `KioskModeApp`: is used to configure a kiosk experience. Users assigned this profile don't access the desktop, but only the Universal Windows Platform (UWP) application or Microsoft Edge running in full-screen above the Lock screen
|
||||
- `KioskModeApp`: is used to configure a kiosk experience. Users assigned this profile execute a Universal Windows Platform (UWP) application or Microsoft Edge running in full-screen
|
||||
- `AllAppList` is used to configure a restricted user experience. Users assigned this profile, access the desktop with the specific apps on the Start menu
|
||||
|
||||
> [!IMPORTANT]
|
||||
|
@ -7,7 +7,36 @@ ms.topic: overview
|
||||
|
||||
# Configure a single-app kiosk with Assigned Access
|
||||
|
||||
<<<<<<< HEAD:windows/configuration/assigned-access/configure-single-app-kiosk.md
|
||||
A single-app kiosk uses the Assigned Access feature to run a single application above the lock screen. When the kiosk account signs in, the app is launched automatically. The person using the kiosk can't do anything on the device outside of the kiosk app.
|
||||
=======
|
||||
Assigned Access is a Windows feature that you can use to configure a device as a kiosk or with a restricted user experience.
|
||||
|
||||
When you configure a **kiosk experience**, a single Universal Windows Platform (UWP) application or Microsoft Edge is executed in full screen. Users can only use that application and once the kiosk app is closed, it automatically restarts. Practical examples include:
|
||||
|
||||
- Public browsing
|
||||
- Interactive digital signage
|
||||
|
||||
When you configure a **restricted user experience**, users can only execute a defined list of applications, with a tailored Start menu and Taskbar. Different policy settings and AppLocker rules are enforced, creating a locked down experience. The users can access a familiar Windows desktop, while limiting their access, reducing distractions, and potential for inadvertent uses. Ideal for shared devices, you can create different configurations for different users. Practical examples include:
|
||||
|
||||
- Frontline worker devices
|
||||
- Student devices
|
||||
- Lab devices
|
||||
|
||||
> [!NOTE]
|
||||
> When you configure a restricted user experience, different policy settings are applied to the device. Some policy settings apply to standard users only, and some to administrator accounts too. For more information, see [Assigned Access policy settings](policy-settings.md).
|
||||
|
||||
## Requirements
|
||||
|
||||
Here are the requirements for Assigned Access:
|
||||
|
||||
- To use a kiosk experience, [User account control (UAC)](/windows/security/identity-protection/user-account-control/user-account-control-overview) must be enabled
|
||||
- To use a kiosk experience, you must sign in from the console. The kiosk experience isn't supported over a remote desktop connection
|
||||
|
||||
[!INCLUDE [assigned-access](../../../includes/licensing/assigned-access.md)]
|
||||
|
||||
## Configure a kiosk experience
|
||||
>>>>>>> 29fc1e82cb8d18c0059926e1e862a382aa6ae7a9:windows/configuration/assigned-access/overview.md
|
||||
|
||||
There are several options to configure a kiosk experience. If you need to configure a single device with a local account, you can use:
|
||||
|
||||
@ -145,7 +174,7 @@ Here are the steps to configure a kiosk using the Settings app:
|
||||
>[!NOTE]
|
||||
>If there are any local standard user accounts already, the **Create an account** dialog offers the option to **Choose an existing account**
|
||||
|
||||
1. Choose the application to run when the kiosk account signs in. Only apps that can run above the lock screen are available in the list of apps to choose from. If you select **Microsoft Edge** as the kiosk app, you configure the following options:
|
||||
1. Choose the application to run when the kiosk account signs in. If you select **Microsoft Edge** as the kiosk app, you configure the following options:
|
||||
|
||||
- Whether Microsoft Edge should display your website full-screen (digital sign) or with some browser controls available (public browser)
|
||||
- Which URL should be open when the kiosk accounts signs in
|
||||
|
@ -23,7 +23,12 @@ When you configure a **restricted user experience**, users can only execute a de
|
||||
> [!NOTE]
|
||||
> When you configure a restricted user experience, different policy settings are applied to the device. Some policy settings apply to standard users only, and some to administrator accounts too. For more information, see [Assigned Access policy settings](policy-settings.md).
|
||||
|
||||
<<<<<<< HEAD
|
||||
## Requirements
|
||||
=======
|
||||
- **Assigned Access**: used to execute a single Universal Windows Platform (UWP) app or Microsoft Edge in full screen. When the kiosk account signs in, the kiosk app launches automatically. If the UWP app is closed, it automatically restarts
|
||||
- **Shell Launcher**: used to configure a device to execute a Windows desktop application as the user interface. The specified application replaces the default Windows shell (`Explorer.exe`) that usually runs when a user signs in
|
||||
>>>>>>> 29fc1e82cb8d18c0059926e1e862a382aa6ae7a9
|
||||
|
||||
Here are the requirements for Assigned Access:
|
||||
|
||||
|
@ -77,7 +77,7 @@ Here are the steps to configure a kiosk using the Settings app:
|
||||
>[!NOTE]
|
||||
>If there are any local standard user accounts already, the **Create an account** dialog offers the option to **Choose an existing account**
|
||||
|
||||
1. Choose the application to run when the kiosk account signs in. Only apps that can run above the lock screen are available in the list of apps to choose from. If you select **Microsoft Edge** as the kiosk app, you configure the following options:
|
||||
1. Choose the application to run when the kiosk account signs in. If you select **Microsoft Edge** as the kiosk app, you configure the following options:
|
||||
|
||||
- Whether Microsoft Edge should display your website full-screen (digital sign) or with some browser controls available (public browser)
|
||||
- Which URL should be open when the kiosk accounts signs in
|
||||
|
@ -116,7 +116,7 @@ The following guidelines help you choose an appropriate Windows app for a kiosk
|
||||
|
||||
- Windows apps must be provisioned or installed for the Assigned Access account before they can be selected as the Assigned Access app. [Learn how to provision and install apps](/windows/client-management/mdm/enterprise-app-management#install_your_apps)
|
||||
- UWP app updates can sometimes change the Application User Model ID (AUMID) of the app. In such scenario, you must update the Assigned Access settings to execute the updated app, because Assigned Access uses the AUMID to determine the app to launch
|
||||
- The app must be able to run above the lock screen. If the app can't run above the lock screen, it can't be used as a kiosk app
|
||||
- The app must be able to run *above* the lock screen. If the app can't run above the lock screen, it can't be used as a kiosk app
|
||||
- Some apps can launch other apps. Assigned Access in kiosk mode prevents Windows apps from launching other apps. Avoid selecting Windows apps that are designed to launch other apps as part of their core functionality
|
||||
- Microsoft Edge includes support for kiosk mode. To learn more, see [Microsoft Edge kiosk mode](/microsoft-edge/deploy/microsoft-edge-kiosk-mode-deploy)
|
||||
- Don't select Windows apps that might expose information you don't want to show in your kiosk, since kiosk usually means anonymous access and locates in a public setting. For example, an app that has a file picker allows the user to gain access to files and folders on the user's system, avoid selecting these types of apps if they provide unnecessary data access
|
||||
|
After Width: | Height: | Size: 114 KiB |
After Width: | Height: | Size: 116 KiB |
135
windows/configuration/background/index.md
Normal file
@ -0,0 +1,135 @@
|
||||
---
|
||||
title: Configure the Desktop and Lock Screen Backgrounds in Windows
|
||||
description: Learn how to configure the desktop and lock screen background in Windows using policy settings, including Intune, CSP, and GPO.
|
||||
ms.topic: how-to
|
||||
ms.date: 03/03/2025
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
appliesto:
|
||||
zone_pivot_groups: windows-versions-11-10
|
||||
---
|
||||
|
||||
# Configure the desktop and lock screen backgrounds
|
||||
|
||||
Configuring desktop and lock screen backgrounds in Windows offers a simple yet effective way to enhance productivity, enforce consistency, and strengthen organizational branding.
|
||||
|
||||
Predefined backgrounds can display company logos, mission statements, or school emblems, reinforcing identity across devices. Examples where predefined backgrounds are especially valuable include kiosks, where lock screens can provide clear instructions, or student devices, where consistent branding fosters a sense of belonging and professionalism.
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
|
||||
:::image type="content" source="images/contoso-lockscreen-11.png" alt-text="Screenshot of the Windows 11 lock screen with Windows spotlight enabled over an organization wallpaper." border="false":::
|
||||
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
|
||||
:::image type="content" source="images/contoso-lockscreen-10.png" alt-text="Screenshot of the Windows 10 lock screen with Windows spotlight enabled over an organization wallpaper." border="false":::
|
||||
|
||||
::: zone-end
|
||||
|
||||
This article explains how to configure the desktop and lock screen backgrounds in Windows using policy settings. It includes examples of how to implement these configurations using Microsoft Intune, Configuration Service Provider (CSP), and Group Policy Object (GPO).
|
||||
|
||||
## Image ratios and scaling
|
||||
|
||||
A key consideration when using custom images is how they appear on devices with varying screen sizes and resolutions. For example, a custom image created in a 16:9 aspect ratio (such as 1600x900) scales properly on devices with 16:9 resolutions, like 1280x720 or 1920x1080. On devices with other aspect ratios, such as 4:3 (1024x768) or 16:10 (1280x800), the image's height scales correctly, but the width is cropped to match the aspect ratio. The image remains centered on the screen.
|
||||
|
||||
Images created in nonstandard aspect ratios might scale and center unpredictably when displayed on devices with different resolutions. To ensure consistent results, especially for images containing text (for example, legal statements), design the image in a 16:9 resolution and keep critical text within the 4:3 region. This approach ensures that the text remains visible across all aspect ratios.
|
||||
|
||||
## Configure the desktop background
|
||||
|
||||
**Windows edition requirements**. The following table summarizes the Windows editions and licensing requirements for configuring the desktop background:
|
||||
|
||||
| Windows edition | Intune/CSP | GPO |
|
||||
|:-|:-:|:-:|
|
||||
|Pro / Pro Education|✅|✅|
|
||||
|Enterprise / Education|✅|✅|
|
||||
|IoT Enterprise|✅|✅|
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune/CSP**](#tab/intune)
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||
|
||||
| Category | Setting name | Value |
|
||||
|--|--|--|
|
||||
| **Personalization** | Desktop Image Url | An http or https URL to a jpg, jpeg, or png image file. |
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [Personalization CSP][CSP-1].
|
||||
|
||||
| Setting |
|
||||
|--------|
|
||||
| - **OMA-URI:** `./Vendor/MSFT/Personalization/DesktopImageUrl`<br>- **Data type:** string <br>- **Value:** An http or https URL to a jpg, jpeg, or png image file. |
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/group-policy.svg" border="false"::: **GPO**](#tab/gpo)
|
||||
|
||||
[!INCLUDE [gpo-settings-1](../../../includes/configure/gpo-settings-1.md)]
|
||||
|
||||
| Group policy path | Group policy setting | Value |
|
||||
| - | - | - |
|
||||
| **User Configuration\Administrative Templates\Desktop\Desktop** |Desktop Wallpaper | Fully qualified path and name of the image file. You can use a local path or a UNC path. |
|
||||
|
||||
[!INCLUDE [gpo-settings-2](../../../includes/configure/gpo-settings-2.md)]
|
||||
|
||||
---
|
||||
|
||||
## Configure the lock screen background
|
||||
|
||||
**Windows edition requirements**. The following table summarizes the Windows editions and licensing requirements for configuring the lock screen background:
|
||||
|
||||
| Windows edition | Intune/CSP | GPO |
|
||||
|:-|:-:|:-:|
|
||||
|Pro / Pro Education|✅|❌|
|
||||
|Enterprise / Education|✅|✅|
|
||||
|IoT Enterprise|✅|✅|
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune/CSP**](#tab/intune)
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||
|
||||
| Category | Setting name | Value |
|
||||
|--|--|--|
|
||||
| **Personalization** | Lock Screen Image Url| An http or https URL to a jpg, jpeg, or png image file. |
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [Personalization CSP][CSP-1].
|
||||
|
||||
| Setting |
|
||||
|--------|
|
||||
| - **OMA-URI:** `./Vendor/MSFT/Personalization/LockScreenImageUrl`<br>- **Data type:** string <br>- **Value:** An http or https URL to a jpg, jpeg, or png image file.|
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/group-policy.svg" border="false"::: **GPO**](#tab/gpo)
|
||||
|
||||
[!INCLUDE [gpo-settings-1](../../../includes/configure/gpo-settings-1.md)]
|
||||
|
||||
| Group policy path | Group policy setting | Value |
|
||||
| - | - | - |
|
||||
| **Computer Configuration\Administrative Templates\Control Panel\Personalization** | Force a specific default lock screen and logon image | Fully qualified path and name of the image file. You can use a local path or a UNC path.|
|
||||
|
||||
[!INCLUDE [gpo-settings-2](../../../includes/configure/gpo-settings-2.md)]
|
||||
|
||||
---
|
||||
|
||||
> [!TIP]
|
||||
> You can also configure a custom lock screen image using [organizational messages in the Microsoft 365 admin center][M365-1].
|
||||
|
||||
## User experience
|
||||
|
||||
When the policy is applied, the lock screen and desktop background images are set to the specified URL or path. The images are downloaded and cached locally on the device. The images are displayed in the background when the user signs in, and on the lock screen when the user locks the device.
|
||||
|
||||
## Windows spotlight
|
||||
|
||||
Windows spotlight is a feature that can display a different image on the lock screen and desktop background every day. Windows spotlight can also provide personalized content, such as tips and tricks for using Windows. You can configure a custom background image or lock screen image and still use Windows spotlight. When you do so, users can still receive suggestions, fun facts, tips, or organizational messages, but the background image is replaced with the custom image.
|
||||
|
||||
To learn more, see [Configure Windows spotlight](../windows-spotlight/index.md).
|
||||
|
||||
<!--links-->
|
||||
|
||||
[CSP-1]: /windows/client-management/mdm/personalization-csp
|
||||
[M365-1]: /microsoft-365/admin/misc/organizational-messages-microsoft-365?view=o365-worldwide
|
||||
[INT-1]: /mem/intune/configuration/settings-catalog
|
After Width: | Height: | Size: 40 KiB |
84
windows/configuration/settings/page-visibility.md
Normal file
@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Configure the Settings Page Visibility in Windows
|
||||
description: Learn how to configure the pages listed in the Windows Settings app.
|
||||
ms.topic: how-to
|
||||
ms.date: 03/03/2025
|
||||
author: paolomatarazzo
|
||||
ms.author: paoloma
|
||||
---
|
||||
|
||||
# Configure the Settings page visibility
|
||||
|
||||
*Settings* is a Windows application that offers a unified interface to manage the system settings. In certain scenarios, you might want to restrict access to specific Settings pages to ensure a more controlled and secure environment. This is especially beneficial for devices used in specific environments, such as kiosks or student devices, where limiting access to certain options can prevent unauthorized changes and maintain a consistent user experience.
|
||||
|
||||
:::image type="content" source="images/settings-page-visibility.png" alt-text="Screenshot of the Settings app configured with a policy setting to limit the categories displayed." border="false":::
|
||||
|
||||
This article explains how to configure the Settings app and how to implement the configurations using Microsoft Intune, Configuration Service Provider (CSP), and Group Policy Object (GPO).
|
||||
|
||||
## Page visibility list policy setting
|
||||
|
||||
You can configure the visibility of Settings pages using the *page visibility list* policy setting. This policy allows you to block a given set of pages from the Settings app. Blocked pages aren't visible in the app and can't be accessed through direct navigation via Uniform Resource Identifier (URI), context menu in Explorer, or other means. Direct navigation to a blocked page results in the first page of Settings displayed instead.
|
||||
|
||||
The page visibility list policy has two modes:
|
||||
|
||||
- **Show Specific Pages**
|
||||
- Start the policy string with `showonly:`
|
||||
- Follow it with a list of Settings page identifiers, separated by semicolons
|
||||
- **Hide Specific Pages**
|
||||
- Start the policy string with `hide:`
|
||||
- Follow it with a list of Settings page identifiers, separated by semicolons
|
||||
|
||||
> [!NOTE]
|
||||
> The identifier for any Settings page is the published URI for that page, minus the `ms-settings:` protocol part. For the list of categories and page identifiers, see [ms-settings: URI scheme reference](https://go.microsoft.com/fwlink/?linkid=2102995#ms-settings-uri-scheme-reference).
|
||||
|
||||
## Examples
|
||||
|
||||
Show only the **About** and **Bluetooth** pages. Their respective URIs are `ms-settings:about` and `ms-settings:bluetooth`:
|
||||
|
||||
`showonly:about;bluetooth`
|
||||
|
||||
Hide only the Bluetooth page, which has the URI `ms-settings:bluetooth`:
|
||||
|
||||
`hide:bluetooth`
|
||||
|
||||
## Configuration
|
||||
|
||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/intune.svg" border="false"::: **Intune/CSP**](#tab/intune)
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||
|
||||
| Category | Setting name | Value |
|
||||
|--|--|--|
|
||||
| **Settings** | - Page Visibility List<br>- Page Visibility List (User)| List of URIs to show or hide, separated by semicolons.|
|
||||
|
||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||
|
||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [Policy CSP][CSP-1].
|
||||
|
||||
| Setting |
|
||||
|--|
|
||||
|- **OMA-URI:** `./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.<br><br>Or<br><br>- **OMA-URI:** `./User/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList`<br>- **Data type:** string<br>- **Value:** List of URIs to show or hide, separated by semicolons.|
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/group-policy.svg" border="false"::: **GPO**](#tab/gpo)
|
||||
|
||||
[!INCLUDE [gpo-settings-1](../../../includes/configure/gpo-settings-1.md)]
|
||||
|
||||
| Group policy path | Group policy setting | Value |
|
||||
| - | - | - |
|
||||
| **Computer Configuration\Administrative Templates\Control Panel**<br><br>Or<br><br>**User Configuration\Administrative Templates\Control Panel** | Settings Page Visibility | List of URIs to show or hide, separated by semicolons.|
|
||||
|
||||
[!INCLUDE [gpo-settings-2](../../../includes/configure/gpo-settings-2.md)]
|
||||
|
||||
---
|
||||
|
||||
## User Experience
|
||||
|
||||
By controlling the visibility of Settings pages, you can create a customized user experience tailored to your organization's specific needs. Once the policy is applied, users have access only to the Settings pages you explicitly allow, ensuring a focused and streamlined interface.
|
||||
|
||||
<!--links-->
|
||||
|
||||
[CSP-1]: /windows/client-management/mdm/policy-csp-settings#pagevisibilitylist
|
||||
[M365-1]: /microsoft-365/admin/misc/organizational-messages-microsoft-365?view=o365-worldwide
|
||||
[INT-1]: /mem/intune/configuration/settings-catalog
|
@ -7,8 +7,12 @@ items:
|
||||
href: start/toc.yml
|
||||
- name: Taskbar
|
||||
href: taskbar/toc.yml
|
||||
- name: Desktop and lock screen backgrounds
|
||||
href: background/index.md
|
||||
- name: Windows spotlight
|
||||
href: windows-spotlight/index.md
|
||||
- name: Settings page visibility
|
||||
href: settings/page-visibility.md
|
||||
- name: Microsoft Store
|
||||
href: store/toc.yml
|
||||
- name: Cellular settings
|
||||
|
Before Width: | Height: | Size: 48 KiB After Width: | Height: | Size: 120 KiB |
Before Width: | Height: | Size: 62 KiB After Width: | Height: | Size: 127 KiB |
@ -94,22 +94,9 @@ Here's a sorted list of the policy settings to configure Windows spotlight:
|
||||
|
||||
## Custom lock screen and background images
|
||||
|
||||
You can replace the Windows spotlight lock screen and background images with a custom image. When you do so, users can still see suggestions, fun facts, tips, or organizational messages on the lock screen, but the background image is replaced with the custom image.
|
||||
You can replace the Windows spotlight lock screen and background images with a custom image. When you do so, users can still receive suggestions, fun facts, tips, or organizational messages, but the background image is replaced with the custom image.
|
||||
|
||||
To configure the lock screen and background images, use the [Personalization CSP][CSP-2].
|
||||
|
||||
|Policy name| CSP | GPO |
|
||||
|-|-|-|
|
||||
|[DesktopImageUrl](/windows/client-management/mdm/personalization-csp#desktopimageurl)|✅|✅|
|
||||
|[LockScreenImageUrl](/windows/client-management/mdm/personalization-csp#lockscreenimageurl)|✅|✅|
|
||||
|
||||
>[!NOTE]
|
||||
> A concern with custom images is how they'll appear on different screen sizes and resolutions. A custom image created in `16:9` aspect ratio (for example, `1600x900`) scales properly on devices using a `16:9` resolution, such as `1280x720` or `1920x1080`. On devices using other aspect ratios, such as `4:3` (`1024x768`) or `16:10` (`1280x800`), height scales correctly and width is cropped to a size equal to the aspect ratio. The image remains centered on the screen.
|
||||
>
|
||||
> Lock screen images created at other aspect ratios might scale and center unpredictably on your device when changing aspect ratios. The recommendation for custom images that include text (such as a legal statement), is to create the lock screen image in `16:9` resolution with text contained in the `4:3` region, allowing the text to remain visible at any aspect ratio.
|
||||
|
||||
> [!TIP]
|
||||
> You also have the option to configure a custom lock screen image using [organizational messages in the Microsoft 365 admin center][M365-1].
|
||||
To learn more, see [Configure the desktop and lock screen background](../background/index.md).
|
||||
|
||||
## User experience
|
||||
|
||||
@ -137,6 +124,5 @@ To learn more about organizational messages, see:
|
||||
<!--links-->
|
||||
|
||||
[CSP-1]: /windows/client-management/mdm/policy-csp-experience
|
||||
[CSP-2]: /windows/client-management/mdm/personalization-csp
|
||||
[INT-1]: /mem/intune/remote-actions/organizational-messages-overview
|
||||
[M365-1]: /microsoft-365/admin/misc/organizational-messages-microsoft-365?view=o365-worldwide
|
||||
|