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: learn-pr/wwl-azure/administer-device-authentication/includes/2-describe-azure-active-directory-join.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
@@ -1,4 +1,4 @@
1
-
Starting with Windows 10 and continuing into Windows 11, in addition to joining an Active Directory Domain Services (AD DS) domain, deploy Microsoft Entra joined devices. Along with creating user accounts in Microsoft Entra ID, you can have objects that represent devices, and you can manage devices that are joined to Microsoft Entra ID from the cloud.
1
+
Starting with Windows 10 and continuing into Windows 11, in addition to joining an Active Directory Domain Services (AD DS) domain, organizations can deploy Microsoft Entra joined devices. Along with creating user accounts in Microsoft Entra ID, you can have objects that represent devices, and you can manage devices that are joined to Microsoft Entra ID from the cloud.
2
2
3
3
Before you decide whether you want to join a device to an AD DS domain or to Microsoft Entra ID, it’s important to understand the difference between these two concepts. Devices that join an AD DS domain must run a supported operating system version; for example, Home editions of the Windows and Windows RT operating systems don't support joining a domain. Devices that are capable of joining an AD DS domain usually access on-premises applications and services. Devices also can access some cloud resources if you integrate the domain accounts and Microsoft accounts.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/enroll-devices-use-intune/includes/8-enroll-ios-devices-intune.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,16 +26,16 @@ If an organization allows its users to bring their own devices, the users should
26
26
27
27
1. Turn on your iOS device.
28
28
2. After you select your **Language**, connect your device to Wi-Fi.
29
-
3. On the **Set up iOS device** screen, choose whether you want to:
30
-
31
-
- Set up as new device
32
-
- Restore from iCloud backup
33
-
- Restore from iTunes backup
34
-
4. Once you’ve connected to Wi-Fi, the **Configuration** screen will appear. This will say:
29
+
3. Once you've connected to Wi-Fi, the **Configuration** screen will appear. This will say:
35
30
36
31
-\[Your Company\] will automatically configure your device.
37
32
- Configuration allows \[Your Company\] to manage this device over the air. An administrator can help you set up email and network accounts, install and configure apps, and manage settings remotely. An administrator may disable features, install and remove apps, monitor and restrict your Internet traffic and remotely erase this device.
38
33
- Configuration is provided by: \[Your Company's\] iOS Team \[Address\]
34
+
4. On the **Set up iOS device** screen, choose whether you want to:
35
+
36
+
- Set up as new device
37
+
- Restore from iCloud backup
38
+
- Restore from iTunes backup
39
39
5.**Log in with your Apple ID**. Logging in lets you install the Company Portal app and install the management profile that will let your company give you access to its resources, such as email and apps.
40
40
6. Agree to the **Terms and Conditions** and decide whether you want to send diagnostic information to Apple.
41
41
7. Once you complete your enrollment, your device may prompt you to take more actions. Some of these steps might be entering your password for email access or setting up a passcode.
Copy file name to clipboardExpand all lines: learn-pr/wwl/deploy-devices-windows-autopilot/includes/4-prepare-device-ids-for-autopilot.md
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,15 +18,9 @@ As discussed earlier, you can create Windows Autopilot deployment profiles in th
18
18
19
19
### Prepare a Microsoft Autopilot deployment
20
20
21
-
You can manage Windows Autopilot deployment by using:
21
+
You manage Windows Autopilot deployment by using Microsoft Intune.
22
22
23
-
- Intune
24
-
- Microsoft Store for Business
25
-
26
-
> [!NOTE]
27
-
> Microsoft Store for Business is a cloud service that organizations of any size can use. Organizations use it to distribute both modern Windows apps that vendors develop for a general audience and line-of-business (LOB) apps that are available only for the organization*.*
28
-
29
-
You must perform the first step—uploading device-specific information, including hardware IDs—in Microsoft Store for Business or Microsoft Intune. If you plan to manage Windows Autopilot in Intune, you’ll have to sync Windows Autopilot devices from Microsoft Store for Business to Intune.
23
+
You must upload device-specific information, including hardware IDs, to Microsoft Intune. You can do this by importing a CSV file or by using the automated methods described in the following sections.
30
24
31
25
To deploy devices by using Windows Autopilot, you must first obtain the CSV file that contains the device-specific information.
32
26
@@ -50,7 +44,7 @@ After installing the script, you can generate device-specific information and sa
50
44
51
45
### Upload the device-specific CSV file
52
46
53
-
To do this, you must have the Admin role in Microsoft Store for Business or Global admin role in Intune. When you upload a CSV file, you'll receive a notification if the upload was successful and the number of devices that were added. If there was any error, for example, if the CSV file wasn't formatted properly or some devices were already in Microsoft Store for Business, you can download the CSV file with error information and URLs that point to detailed error descriptions, and then you can review the details.
47
+
To upload a CSV file to Microsoft Intune, you must have the Intune Administrator role or Global Administrator role. When you upload a CSV file, you'll receive a notification if the upload was successful and the number of devices that were added. If there was any error, for example, if the CSV file wasn't formatted properly or some devices were already registered, you can download the CSV file with error information and URLs that point to detailed error descriptions, and then you can review the details.
54
48
55
49
When you upload a CSV file, you can add devices to an existing Windows Autopilot deployment group, create a new Windows Autopilot deployment group for the devices, or add them without using groups. You can use groups when you want to apply the same deployment settings to multiple devices at once.
0 commit comments