Skip to content

Commit 05084f7

Browse files
authored
Apply suggestions from code review
1 parent 54b3d73 commit 05084f7

4 files changed

Lines changed: 6 additions & 6 deletions

File tree

memdocs/intune/configuration/administrative-templates-restrict-usb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,13 +66,13 @@ Applies to:
6666

6767
In the following example, the **Keyboard**, **Mouse**, and **Multimedia** classes are allowed:
6868

69-
:::image type="content" source="media/administrative-templates-restrict-usb/allow-installation-of-devices-using-drivers-setting.png" alt-text="In Intune, set the Allow installation of devices using drivers that match these device setup classes setting, and add your class GUIDs.":::
69+
:::image type="content" source="media/administrative-templates-restrict-usb/allow-installation-of-devices-using-drivers-setting.png" alt-text="Screenshot that shows how to set the Allow installation of devices using drivers that match these device setup classes setting in Intune and how to add your class GUIDs.":::
7070

7171
Select **OK**.
7272

7373
- **Allow installation of devices that match any of these Device IDs**: Select **Enabled**. Then, add the device/hardware IDs for devices you want to allow:
7474

75-
:::image type="content" source="media/administrative-templates-restrict-usb/allow-installation-of-devices-that-match-setting.png" alt-text="In Intune, set the Allow installation of devices that match any of these Device IDs setting, and add your hardware IDs.":::
75+
:::image type="content" source="media/administrative-templates-restrict-usb/allow-installation-of-devices-that-match-setting.png" alt-text="Screenshot that shows how to set the Allow installation of devices that match any of these Device IDs setting in Intune and how to add your hardware IDs.":::
7676

7777
To get the device/hardware ID, you can use Device Manager, find the device, and look at the properties. For the specific steps, see [find the hardware ID on a Windows device](/windows-hardware/drivers/install/hardware-ids).
7878

memdocs/intune/configuration/device-profile-assign.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ Use the following matrix to understand support for excluding groups:
154154
- ❌: Not supported
155155
- ❕ : Partially supported
156156

157-
:::image type="content" source="./media/device-profile-assign/include-exclude-user-device-groups-matrix.png" alt-text="Image that shows the supported options to include or exclude groups from a profile assignment.":::
157+
:::image type="content" source="./media/device-profile-assign/include-exclude-user-device-groups-matrix.png" alt-text="Screenshot that shows the supported options to include or exclude groups from a profile assignment.":::
158158

159159
| Scenario | Support|
160160
| --- | --- |

memdocs/intune/configuration/device-profile-create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ When creating profiles, consider the following recommendations:
216216

217217
The following image shows an example of a setting that can apply to users, apply to devices, or apply to both:
218218

219-
:::image type="content" source="./media/device-profile-create/setting-applies-to-user-and-device.png" alt-text="Image that shows an Intune admin template that applies to user and devices in Microsoft Intune.":::
219+
:::image type="content" source="./media/device-profile-create/setting-applies-to-user-and-device.png" alt-text="Screenshot that shows an Intune admin template that applies to user and devices in Microsoft Intune.":::
220220

221221
- Every time you create a restrictive policy, communicate this change to your users. For example, if you're changing the passcode requirement from four (4) characters to six (6) characters, let your users know before your assign the policy.
222222

windows-365/enterprise/create-azure-network-connection.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,11 @@ To create an ANC, you must:
5555
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **Azure network connection** > **Create**.
5656
2. Depending on the type of ANC you want to create, choose **Azure AD Join** or **Hybrid Azure AD Join**.
5757

58-
![Screenshot of create connection dropdown](./media/create-azure-network-connection/create-connection-dropdown.png)
58+
![Screenshot of create connection dropdown.](./media/create-azure-network-connection/create-connection-dropdown.png)
5959

6060
3. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
6161

62-
![Screenshot of Name field](./media/create-azure-network-connection/connection-name.png)
62+
![Screenshot of Name field.](./media/create-azure-network-connection/connection-name.png)
6363

6464
4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy ANC](health-checks.md), you won't be able to proceed.
6565
5. Select a **Virtual network** and **Subnet**.

0 commit comments

Comments
 (0)