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
> Custom configuration profiles shouldn't be used for sensitive information, such as WiFi connections or authenticating apps, sites, and more. Instead, use the built-in profiles for sensitive information, as they're designed and configured to handle sensitive information.
35
-
>
35
+
>
36
36
> For example, use the built-in [Wi-Fi profile](wi-fi-settings-configure.md) to deploy a Wi-Fi connection. Use the built-in [certificates profile](../protect/certificates-configure.md) for authentication.
37
37
38
38
Using Microsoft Intune, you can add or create custom settings for your iOS/iPadOS devices using "custom profiles". Custom profiles are a feature in Intune. They're designed to add device settings and features that aren't built in to Intune.
> Custom configuration profiles shouldn't be used for sensitive information, such as WiFi connections or authenticating apps, sites, and more. Instead, use the built-in profiles for sensitive information, as they're designed and configured to handle sensitive information.
34
-
>
34
+
>
35
35
> For example, use the built-in [Wi-Fi profile](wi-fi-settings-configure.md) to deploy a Wi-Fi connection. Use the built-in [certificates profile](../protect/certificates-configure.md) for authentication.
36
36
37
37
Using Microsoft Intune, you can add or create custom settings for your macOS devices using a "custom profile". Custom profiles are a feature in Intune. They're designed to add device settings and features that aren't built in to Intune.
- Add [macOS devices](https://help.apple.com/profilemanager/mac/5.7/#/pm9onzap1984) in Profile Manager.
60
60
- After you add a device in Profile Manager, go to **Under the Library** > **Devices** > select your device > **Settings**. Enter the general, security, privacy, directory, and certificate settings for the device.
61
61
62
-
Download and save this file. You'll enter this file in the Intune profile.
62
+
Download and save this file. You'll enter this file in the Intune profile.
63
63
64
64
- Be sure the settings you export from the Apple Profile Manager are compatible with the macOS version on the devices. For information on resolving incompatible settings, search for **Configuration Profile Reference** and **Mobile Device Management Protocol Reference** on the [Apple Developer](https://developer.apple.com/) website.
-**Configuration profile name**: Enter a name for the policy. This name is shown on the device, and in the Intune status.
69
69
-**Deployment channel**: Select the channel you want to use to deploy your configuration profile. If you send the profile down the wrong channel, deployment could fail. After you select a channel and save the profile, the channel can't be changed. To select a different channel, create a new profile.
70
70
71
-
User-targeted payloads will not apply to devices enrolled without user affinity. For more information on whether a payload can be used for a device configuration profile or a user configuration profile, see [Profile-Specific Payload Keys](https://developer.apple.com/documentation/devicemanagement/profile-specific_payload_keys) on the Apple Developer website.
71
+
User-targeted payloads will not apply to devices enrolled without user affinity. For more information on whether a payload can be used for a device configuration profile or a user configuration profile, see [Profile-Specific Payload Keys](https://developer.apple.com/documentation/devicemanagement/profile-specific_payload_keys) on the Apple Developer website.
72
72
73
73
-**Configuration profile file**: Browse to the `.xml` or `.mobileconfig` file you created using the Apple Configurator or Apple Profile Manager. The max file size is 1000000 bytes (just under 1 MB). The file you import is shown. You can also **Remove** a file after it's been added.
Copy file name to clipboardExpand all lines: memdocs/intune/configuration/custom-settings-windows-10.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
@@ -83,14 +83,14 @@ There's a complete list of all configuration service providers (CSPs) that Windo
83
83
Not all settings are compatible with all Windows client versions. [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference) tells you which versions are supported for each CSP.
84
84
85
85
Additionally, Intune doesn't support all the settings listed in [Configuration service provider reference](/windows/client-management/mdm/configuration-service-provider-reference). To find out if Intune supports the setting you want, open the article for that setting. Each setting page shows its supported operation. To work with Intune, the setting must support the **Add**, **Replace**, and **Get** operations. If the value returned by the **Get** operation doesn't match the value supplied by the **Add** or **Replace** operations, then Intune reports a compliance error.
86
-
86
+
87
87
> [!NOTE]
88
88
> For settings that were created by using a string, base64, or XML data type, the stored value is obscured. If the user who is accessing the value has any of the following permissions or roles, they can see the value:
89
89
>
90
90
> - Create, Read, and Update permissions in a Microsoft Endpoint Manager role-based access control (RBAC) role.
91
91
> - Intune Service Administrator.
92
92
> - Global Administrator Azure Active Directory role.
93
-
>
93
+
>
94
94
> For more information, see [RBAC with Microsoft Intune](../fundamentals/role-based-access-control.md).
0 commit comments