Msft intune device features configuration policy ios (new module) #5739
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Unsure what these properties map to in GUI, if anything? couldn't figure out how to populate them
|
I've a number of pull requests in that haven't been looked at in a couple of weeks, so I'm bumping this one as well! |
FabienTschanz
suggested changes
Feb 13, 2025
...s/Microsoft365DSC/Examples/Resources/IntuneDeviceFeaturesConfigurationPolicyIOS/1-Create.ps1
Outdated
Show resolved
Hide resolved
...s/Microsoft365DSC/Examples/Resources/IntuneDeviceFeaturesConfigurationPolicyIOS/2-Update.ps1
Outdated
Show resolved
Hide resolved
...s/Microsoft365DSC/Examples/Resources/IntuneDeviceFeaturesConfigurationPolicyIOS/3-Remove.ps1
Outdated
Show resolved
Hide resolved
...uneDeviceFeaturesConfigurationPolicyIOS/MSFT_IntuneDeviceFeaturesConfigurationPolicyIOS.psm1
Show resolved
Hide resolved
...uneDeviceFeaturesConfigurationPolicyIOS/MSFT_IntuneDeviceFeaturesConfigurationPolicyIOS.psm1
Outdated
Show resolved
Hide resolved
...uneDeviceFeaturesConfigurationPolicyIOS/MSFT_IntuneDeviceFeaturesConfigurationPolicyIOS.psm1
Outdated
Show resolved
Hide resolved
...uneDeviceFeaturesConfigurationPolicyIOS/MSFT_IntuneDeviceFeaturesConfigurationPolicyIOS.psm1
Outdated
Show resolved
Hide resolved
...uneDeviceFeaturesConfigurationPolicyIOS/MSFT_IntuneDeviceFeaturesConfigurationPolicyIOS.psm1
Show resolved
Hide resolved
Includes changes in all resolved conversations
also added processing for SingleSignOnSettings as noticed an issue
dannyKBjj
added a commit
to dannyKBjj/Microsoft365DSC
that referenced
this pull request
Feb 18, 2025
… for microsoft#5739 Despite trying to sync with dev PR 5739 fails all Export-DSC unit tests. Works fine in this new branch despite all code being identical. Submitting this and closing the other one.
Unsure if something has changed, as I swear I tested this previously, but since upgrading to latest version my module wasn't treating certain CIM values as string, even though that's how the mof defined it, thus causing Test- to fail... either way, I spotted the problem and fixed. Devices>Configuration>iOS>Device Features>Single Sign-on app extension>Additional Configuration now correctly handles boolean, string and integer values from the same class definition.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Adds support for Devices>Configuration>iOS>Templates>Device Features (#microsoft.graph.iosDeviceFeaturesConfiguration)
This Pull Request (PR) fixes the following issues
Initial release
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).