You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Create a Universal Print policy in Microsoft Intune
31
31
32
32
> [!NOTE]
33
-
> This feature will release over several days and won't be available to all customers immediately.
33
+
> This feature will release over several days and won't be available to all tenants immediately.
34
34
35
35
Many organizations are moving their printer infrastructure to the cloud. [Universal Print](/universal-print/fundamentals/universal-print-whatis) is a cloud-based printing solution in Microsoft 365. It uses built-in cloud printers, built-in legacy printers, and runs entirely in Microsoft Azure.
36
36
@@ -60,9 +60,11 @@ This article shows you how to create a Universal Print policy in Microsoft Intun
60
60
-**Printer Administrator** or **Global Administrator** roles: Needed to add printers.
61
61
62
62
For more information on these roles, go to [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference).
63
+
63
64
-**Intune Administrator** or **Global Administrator** roles: Needed to create and assign Intune policies.
64
65
65
66
For more information on these roles, go to [Role-based access control (RBAC) with Microsoft Intune](../fundamentals/role-based-access-control.md)
67
+
66
68
- An assigned Universal Print license.
67
69
68
70
- End user accounts need the following permissions/licenses:
@@ -72,6 +74,8 @@ This article shows you how to create a Universal Print policy in Microsoft Intun
72
74
73
75
If the profile is assigned to an Azure AD user/user group that can't access the printers because of permissions, then Intune grants the assigned user/user group the permissions.
74
76
77
+
- These settings use the [UniversalPrint CSP](/windows/client-management/mdm/universalprint-csp).
78
+
75
79
## Create the policy
76
80
77
81
This policy includes your printer information. When you assign the policy, the printers are automatically installed. Then, on their devices, users select a printer that you added.
Copy file name to clipboardExpand all lines: memdocs/intune/enrollment/windows-bulk-enroll.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,9 @@ Azure AD users are standard users on these devices and receive assigned Intune p
70
70
6. Select **Enroll in Azure AD**, enter a **Bulk Token Expiry** date, and then select **Get Bulk Token**. The token validity period is 180 days.
71
71

72
72
73
+
> [!NOTE]
74
+
> Once a provisioning package is created, it can be revoked before its expiration by removing the associated package_{GUID} user account from Azure AD.
75
+
73
76
7. Provide your Azure AD credentials to get a bulk token.
74
77

Copy file name to clipboardExpand all lines: memdocs/intune/fundamentals/in-development.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ Feedback settings will be provided to address M365 enterprise feedback policies
79
79
You will be able to select to include **Photo Library** as a supported application storage service for *outgoing* data. This support is in addition to *incoming* data transfer support for **Photo Library**. By selecting **Photo Library** in the **Allow users to open data from selected services** setting within Intune, you can allow managed accounts to send *outgoing* data to their device's photo library from their managed apps on iOS and Android platforms. In [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Apps** > **App protection policies** > **Create Policy**. Choose either **iOS/iPadOS** or **Android**. This setting will be available as part of the **Data protection** step and specifically for **Policy managed apps**. For related information, see [Data protection](../apps/app-protection-framework.md#data-protection-2).
80
80
81
81
### Use App Protection Policies with Android Enterprise dedicated devices and Android (AOSP) devices<!-- 13819227 -->
82
-
Intune-managed Android Enterprise dedicated devices enrolled with Azure Active Directory (Azure AD) shared mode and Android (AOSP) devices will be able to receive app protection policies policies and can be targeted separately from other Android device types. For more information about Android Enterprise dedicated devices and Android (AOSP), see [Android Enterprise dedicated devices](../fundamentals/deployment-guide-enrollment-android.md#android-enterprise-dedicated-devices) and [Android Open Source Project](../fundamentals/deployment-guide-enrollment-android.md#android-open-source-project).
82
+
Intune-managed Android Enterprise dedicated devices enrolled with Azure Active Directory (Azure AD) shared mode and Android (AOSP) devices will be able to receive app protection policies and can be targeted separately from other Android device types. For more information about Android Enterprise dedicated devices and Android (AOSP), see [Android Enterprise dedicated devices](../fundamentals/deployment-guide-enrollment-android.md#android-enterprise-dedicated-devices) and [Android Open Source Project](../fundamentals/deployment-guide-enrollment-android.md#android-open-source-project).
For more information, see [Using Azure Virtual Desktop multi-session with Microsoft Intune](../fundamentals/azure-virtual-desktop-multi-session.md)
100
100
101
101
### Remotely restart and shut down macOS device <!-- 12472418 -->
102
-
You'll be able to remotely restart or shutdown a macOS device using device actions. These device actions are available for devices running macOS 10.13 and later.
102
+
You'll be able to remotely restart or shut down a macOS device using device actions. These device actions are available for devices running macOS 10.13 and later.
103
103
For more information, see [Restart devices with Microsoft Intune](../remote-actions/device-restart.md).
We’re changing what Intune displays when you view certificate details for devices and certificate profiles. [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Monitor** > **Certificates**.
119
119
120
-
Today, the certificate reports can show certificates that are no longer valid, or that are no longer on a device. With this change, you’ll won't see information for those invalid certificates. Instead, Intune displays only those that are valid, that were revoked within the last 30 days, or that expired within the last 30 days will be shown.
120
+
Today, the certificate reports can show certificates that are no longer valid, or that are no longer on a device. With this change, you won't see information for those invalid certificates. Instead, Intune displays only those that are valid, that were revoked within the last 30 days, or that expired within the last 30 days will be shown.
121
121
122
122
### View a managed device's group membership<!-- 4100067 -->
123
123
In the monitor section of the **Devices** workload of Intune, you'll be able to view the group membership of all AAD groups for a managed device. When this is available, you will be able to select **Group Membership** by signing in to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and selecting **Devices** > **Monitor** > *select a device* > **Group Membership**.
@@ -40,6 +40,8 @@ Use the information and procedures in this article to configure integration of M
40
40
41
41
Before starting, your environment must meet the [prerequisites](../protect/advanced-threat-protection.md#prerequisites) to use Microsoft Defender for Endpoint with Intune.
42
42
43
+
In addition to managing settings for Microsoft Defender for Endpoint on devices you manage with Intune, you can manage Defender for Endpoint security configurations on devices that aren’t enrolled with Intune. This scenario is called *Security Management for Microsoft Defender for Endpoint* and requires configuring the *Allow Microsoft Defender for Endpoint to enforce Endpoint Security Configurations* toggle to *On*. For more information, see [MDE Security Configuration Management](../protect/mde-security-integration.md).
44
+
43
45
## Enable Microsoft Defender for Endpoint in Intune
44
46
45
47
The first step you take is to set up the service-to-service connection between Intune and Microsoft Defender for Endpoint. Set up requires administrative access to both the Microsoft Defender Security Center, and to Intune.
@@ -52,7 +54,7 @@ You only need to enable Microsoft Defender for Endpoint a single time per tenant
52
54
53
55
2. Select **Endpoint security** > **Microsoft Defender for Endpoint**, and then select **Open the Microsoft Defender for Endpoint admin console**.
54
56
55
-
This opens the **Microsoft 365 Defender** portal at *security.microsoft.com*, which [replaces the use of the previous portal](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide) at *securitycenter.windows.com*.
57
+
This opens the **Microsoft 365 Defender** portal at *security.microsoft.com*, which [replaces the use of the previous portal](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide&preserve-view=true) at *securitycenter.windows.com*.
56
58
57
59
> [!TIP]
58
60
> If the **Connection status** at the top of the page is already set to **Enabled**, the connection to Intune has already been made, and the admin center displays different UI than in the following screen shot. In this event, you can use the link **Open the Microsoft Defender for Endpoint admin console** to open the Microsoft Defender Security Center and use the guidance in the following step to confirm that the **Microsoft Intune connection** is set to **On**.
Copy file name to clipboardExpand all lines: memdocs/intune/protect/antivirus-microsoft-defender-settings-windows-tenant-attach.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -327,7 +327,7 @@ Learn more
327
327
328
328
-**Allow users to view full History results**
329
329
> [!NOTE]
330
-
> This is a legacy setting that only applies to versions of Windows prior to Windows 10 version 1703. User of this setting with a current operating system has no effect. This setting is scheduled for removal from this policy. For more information, see **-DisablePrivacyMode** in [Set-MpPreference](/powershell/module/defender/set-mppreference?view=windowsserver2022-ps) in the Windows PowerShell documentation.
330
+
> This is a legacy setting that only applies to versions of Windows prior to Windows 10 version 1703. User of this setting with a current operating system has no effect. This setting is scheduled for removal from this policy. For more information, see **-DisablePrivacyMode** in [Set-MpPreference](/powershell/module/defender/set-mppreference?view=windowsserver2022-ps&preserve-view=true) in the Windows PowerShell documentation.
Copy file name to clipboardExpand all lines: memdocs/intune/protect/atp-manage-vulnerabilities.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ Following is an example workflow for an application. This same general workflow
94
94
95
95
## Work with security tasks
96
96
97
-
Before you can work with security tasks, they must be created from within the Defender Security Center. For information on using the Microsoft Defender Security Center to create security tasks, see [Remediate vulnerabilities with threat and vulnerability management](/microsoft-365/security/defender-endpoint/tvm-remediation?view=o365-worldwide#request-remediation) in the Defender for Endpoint documentation.
97
+
Before you can work with security tasks, they must be created from within the Defender Security Center. For information on using the Microsoft Defender Security Center to create security tasks, see [Remediate vulnerabilities with threat and vulnerability management](/microsoft-365/security/defender-endpoint/tvm-remediation?view=o365-worldwide&preserve-view=true#request-remediation) in the Defender for Endpoint documentation.
4. On **Settings**, configure the following behavior for the script:
64
64
65
65
-**Run this script using the logged on credentials** – By default, the script runs in the System context on the device. Set this to Yes to have it run in the context of the logged-on user. If the user isn’t logged in, the script defaults back to the System context.
66
-
-**Enforce script signature check** – For more information, see [about_Signing](/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.1) in the PowerShell documentation.
66
+
-**Enforce script signature check** – For more information, see [about_Signing](/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.1&preserve-view=true) in the PowerShell documentation.
67
67
-**Run script in 64 bit PowerShell Host** – By default, the script runs using the 32-bit PowerShell host. Set this to *Yes* to force the script to run using the 64-bit host instead.
68
68
69
69
5. Complete the script creation process. The script is now visible in the *Scripts* pane of the Microsoft Endpoint Manager admin center and will be available to select when configuring compliance policies.
Copy file name to clipboardExpand all lines: memdocs/intune/protect/lookout-mobile-threat-defense-connector.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,8 +56,8 @@ Lookout's mobile app, **Lookout for work**, is installed and run on mobile devic
56
56
57
57
The following platforms are supported for Lookout when enrolled in Intune:
58
58
59
-
-**Android 4.1 and later**
60
-
-**iOS 8 and later**
59
+
-**Android 5.0 and later**
60
+
-**iOS 12 and later**
61
61
62
62
For additional information about platform and language support, visit the [Lookout website](https://personal.support.lookout.com/hc/articles/114094140253).
0 commit comments