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
Copy file name to clipboardExpand all lines: memdocs/autopilot/windows-autopilot-hybrid.md
+3-1
Original file line number
Diff line number
Diff line change
@@ -288,7 +288,9 @@ Autopilot deployment profiles are used to configure the Autopilot devices.
288
288
289
289
13. Select **Next** > **Create**.
290
290
291
-
It takes about 15 minutes for the device profile status to change from *Not assigned* to *Assigning* and, finally, to *Assigned*.
291
+
> [!NOTE]
292
+
>
293
+
>Intune will periodically check for new devices in the assigned groups, and then begin the process of assigning profiles to those devices. Due to several different factors involved in the process of Autopilot profile assignment, an estimated time for the assignment can vary from scenario to scenario. These factors can include AAD groups, membership rules, hash of a device, Intune and Autopilot service, and internet connection. The assignment time will vary depending on all the factors and variables involved in a specific scenario.
Copy file name to clipboardExpand all lines: memdocs/intune/enrollment/windows-bulk-enroll.md
+15-12
Original file line number
Diff line number
Diff line change
@@ -56,38 +56,41 @@ Azure AD users are standard users on these devices and receive assigned Intune p
56
56
1. Download [Windows Configuration Designer (WCD)](https://www.microsoft.com/p/windows-configuration-designer/9nblggh4tx22) from the Microsoft Store.
57
57
58
58
59
-
2. Open the **Windows Configuration Designer** app and select **Provision desktop devices**.
59
+
1. Open the **Windows Configuration Designer** app and select **Provision desktop devices**.
60
60
61
61
62
-
3. A **New project** window opens where you specify the following information:
62
+
1. A **New project** window opens where you specify the following information:
63
63
-**Name** - A name for your project
64
64
-**Project folder** - Save location for the project
65
65
-**Description** - An optional description of the project
66
66
67
67
68
-
4. Enter a unique name for your devices. Names can include a serial number (%SERIAL%) or a random set of characters. Optionally, you can also enter a product key if you are upgrading the edition of Windows, configure the device for shared use, and remove pre-installed software.
68
+
1. Enter a unique name for your devices. Names can include a serial number (%SERIAL%) or a random set of characters. Optionally, you can also enter a product key if you are upgrading the edition of Windows, configure the device for shared use, and remove pre-installed software.
69
69
70
70
71
71
72
-
5. Optionally, you can configure the Wi-Fi network devices connect to when they first start. If the network devices aren't configured, a wired network connection is required when the device is first started.
72
+
1. Optionally, you can configure the Wi-Fi network devices connect to when they first start. If the network devices aren't configured, a wired network connection is required when the device is first started.
73
73
74
74
75
-
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.
75
+
1. Select **Enroll in Azure AD**, enter a **Bulk Token Expiry** date, and then select **Get Bulk Token**. The token validity period is 180 days.
76
76
77
77
78
-
> [!NOTE]
79
-
> Once a provisioning package is created, it can be revoked before its expiration by removing the associated package_{GUID} user account from Azure AD.
78
+
> [!NOTE]
79
+
> Once a provisioning package is created, it can be revoked before its expiration by removing the associated package_{GUID} user account from Azure AD.
80
80
81
-
7. Provide your Azure AD credentials to get a bulk token.
81
+
1. Provide your Azure AD credentials to get a bulk token.
82
82
83
83
84
-
8. In the **Stay signed in to all your apps** page, select **No, sign in to this app only**. If you keep the check box selected and press OK, the device you are using will become managed by your organization. If you do not intend for your device to be managed, make sure to select **No, sign in to this app only**.
84
+
> [!NOTE]
85
+
> The account used to request the bulk token must be included in the [MDM user scope](windows-enroll.md#enable-windows-automatic-enrollment) that is specified in Azure AD.
86
+
87
+
1. In the **Stay signed in to all your apps** page, select **No, sign in to this app only**. If you keep the check box selected and press OK, the device you are using will become managed by your organization. If you do not intend for your device to be managed, make sure to select **No, sign in to this app only**.
85
88
86
-
9. Click **Next** when **Bulk Token** is fetched successfully.
89
+
1. Click **Next** when **Bulk Token** is fetched successfully.
87
90
88
-
10. Optionally, you can **Add applications** and **Add certificates**. These apps and certificates are provisioned on the device.
91
+
1. Optionally, you can **Add applications** and **Add certificates**. These apps and certificates are provisioned on the device.
89
92
90
-
11. Optionally, you can password protect your provisioning package. Click **Create**.
93
+
1. Optionally, you can password protect your provisioning package. Click **Create**.
91
94
Copy file name to clipboardExpand all lines: memdocs/intune/fundamentals/whats-new.md
+18
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,24 @@ You can use RSS to be notified when this page is updated. For more information,
70
70
71
71
### Device configuration
72
72
73
+
#### Support for Locate device on Android Enterprise corporate owned fully managed and Android Enterprise corporate owned work profile devices<!--12391424 -->
74
+
75
+
You can now use "Locate device" on Android Enterprise corporate owned fully managed and Android Enterprise corporate owned work profile devices. With this feature, admins will be able to locate lost or stolen corporate devices on-demand.
76
+
77
+
To do this, in [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), you will need to turn the feature on using **Device Restrictions** in **Device Configuration** for Android Enterprise.
78
+
79
+
Click **Allow** on the **Locate device** toggle for fully managed and corporate owned work profile devices and select applicable groups. **Locate device** will be available when you select **Devices**, and then select **All devices**. From the list of devices you manage, select a supported device, and choose the **Locate device** remote action.
80
+
81
+
For information on locating lost or stolen devices with Intune, go to:
82
+
83
+
-[Locate lost or stolen devices with Intune](../remote-actions/device-locate.md)
Copy file name to clipboardExpand all lines: memdocs/intune/remote-actions/device-locate.md
+13-7
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ You need to enable Windows location services in Windows Out of Box Experience (O
44
44
45
45
**Locate device** - The following platforms support this capability:
46
46
47
-
-**Android Enterprisededicated devices** – Requires the device run *Google Play Services* version **20.06.16** or later and have Location services turned on.
47
+
-**Android Enterprise** – This is applicable to dedicated devices, fully-managed, and corporate-owned work profile devices. Requires the device to run *Google Play Services* version **20.06.16** or later and have Location services turned on.
48
48
-**iOS/iPadOS 9.3 and later** - Requires the device to be in supervised mode, and be in [lost mode](device-lost-mode.md).
49
49
-**Windows 10**:
50
50
- Version 20H2 (10.0.19042.789) or later
@@ -57,8 +57,8 @@ You need to enable Windows location services in Windows Out of Box Experience (O
57
57
58
58
-**iOS/iPadOS 9.3 and later** - Requires the device to be in supervised mode, and be in [lost mode](device-lost-mode.md)
59
59
-**Android Enterprise dedicated devices** - Requires the Intune app running 2202.01 or later
60
-
-**Android Enterprise corporate-owned work profile (COPE) devices** - Requires the Intune app running 2202.01 or later
61
-
-**Android Enterprise corporate-owned fully managed (COBO) devices** - Requires the Intune app running 2202.01 or later
60
+
-**Android Enterprise corporate-owned work profile devices** - Requires the Intune app running 2202.01 or later
61
+
-**Android Enterprise corporate-owned fully managed devices** - Requires the Intune app running 2202.01 or later
62
62
63
63
**Unsupported** - Device location capabilities aren't supported for the following platforms:
64
64
@@ -77,8 +77,6 @@ You need to enable Windows location services in Windows Out of Box Experience (O
77
77
1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
78
78
2. Select **Devices**, and then select **All devices**.
79
79
3. From the list of devices you manage, select a supported device, and choose **...**. Then choose the **Locate device** remote action.
80
-
81
-
82
80
4. After the device is located, its location is shown in **Locate device**.
83
81
84
82
- You can select the location pin on the map to view a location address and coordinates.
@@ -87,6 +85,13 @@ You need to enable Windows location services in Windows Out of Box Experience (O
87
85
88
86
89
87
88
+
Android use of **Locate device** is controlled by **Device Restrictions** in **Device Configuration**.
89
+
There are two separate toggles, one for dedicated and one for fully managed and corporate owned work profile devices.
90
+
91
+
For fully managed and corporate owned work profile, **Locate device** is set to **Not configured** as the default and it blocks the feature. To allow this feature, use device restrictions within Device Configuration and configure the toggle for **Locate device** to Allow.
92
+
93
+
For dedicated devices, **Locate device** is set to **Not configured** as the default, which allows the feature. To turn this feature off, use device restrictions within **Device Configuration** and configure the toggle for **Locate device** to **Block**. When **Locate device** is allowed, users will receive a one-time notification, "Intune can access your location", indicating that Intune has the ability to use location permissions on the device.
94
+
90
95
### Last known location
91
96
92
97
When you use the *Locate device* action for an Android Enterprise dedicated device that is off-line and unable to respond with its current location, Intune attempts to display its last known location. This capability uses data submitted by the device when it checks in with Intune.
@@ -117,14 +122,14 @@ To start a lost device sound alert:
117
122
4. On the devices *Overview* pane:
118
123
- For **iOS/iPadOS**: select **Play Lost mode sound (supervise only)**. The sound plays on an iOS/iPadOS device until the device is removed from lost mode.
119
124
120
-
- For **Android Enterprise dedicated devices**, **Android Enterprise corporate-owned work profile (COPE) devices**, and **Android Enterprise corporate-owned fully managed (COBO) devices** : select **Play Lost device sound**. The sound plays on an Android Enterprise dedicated device for the set duration or if notifications are enabled, until a user on the device turns it off.
125
+
- For **Android Enterprise dedicated devices**, **Android Enterprise corporate-owned work profile devices**, and **Android Enterprise corporate-owned fully managed devices** : select **Play Lost device sound**. The sound plays on an Android Enterprise dedicated device for the set duration or if notifications are enabled, until a user on the device turns it off.
121
126
122
127
- For **Android Enterprise dedicated devices**:
123
128
- devices running on operating systems below version 10, a full screen activity with a **Stop Sound** button pops up.
124
129
- devices running on operating systems version 10 or higher, if notifications are enabled, a notification with a **Stop Sound** button shows up.
125
130
- To configure system notifications for devices in kiosk mode, see [Android Enterprise device settings to allow or restrict features using Intune](../configuration/device-restrictions-android-for-work.md).
126
131
127
-
- For **Android Enterprise corporate-owned work profile (COPE) devices**, and **Android Enterprise corporate-owned fully managed (COBO) devices** :
132
+
- For **Android Enterprise corporate-owned work profile devices**, and **Android Enterprise corporate-owned fully managed devices** :
128
133
- To configure system notifications for devices, see [Android Enterprise device settings to allow or restrict features using Intune](../configuration/device-restrictions-android-for-work.md).
129
134
130
135
## Security and privacy information for lost mode and locate device actions
@@ -135,6 +140,7 @@ To start a lost device sound alert:
135
140
- The data for last known locations is stored for up to seven days, and then removed.
136
141
- Location data is encrypted, both while stored and while being transmitted.
137
142
- For iOS/iPadOS devices, when you configure lost mode, you can customize a message that appears on the lock screen. In this message, to help the person that finds the device, be sure to include specific details to return the lost device.
143
+
- For fully-managed and corporate-owned work profile scenarios, end users will receive a notification when the administrator uses this feature, if notifications have been enabled.
0 commit comments