Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with inverted comma in Name parameter in MSFT_MicrosoftGraphapplistitem in IntuneDeviceConfigurationPolicy #3117

Closed
maheshdalavi opened this issue Apr 1, 2023 · 1 comment · Fixed by #3129 or #3140
Assignees
Labels
Bug Something isn't working Intune

Comments

@maheshdalavi
Copy link

Details of the scenario you tried and the problem that is occurring

  • If we have a name in “MSFT_MicrosoftGraphapplistitem” with in "IntuneDeviceConfigurationPolicy" an inverted comma in it will result in LCM failure.

image

Verbose logs showing the problem

While configuring the LCM gives the below error.

image

Suggested solution to the issue

The DSC configuration that is used to reproduce the issue (as detailed as possible)

The operating system the target node is running

Get-ComputerInfo -Property @(
    'OsName',
    'OsOperatingSystemSKU',
    'OSArchitecture',
    'WindowsVersion',
    'WindowsBuildLabEx',
    'OsLanguage',
    'OsMuiLanguages')

Version of the DSC module that was used ('dev' if using current dev branch)

@andikrueger
Copy link
Collaborator

Just to be sure: The configuration you are using is the result of an export?

@andikrueger andikrueger added Bug Something isn't working Intune labels Apr 3, 2023
NikCharlebois added a commit to NikCharlebois/Microsoft365DSC that referenced this issue Apr 3, 2023
@NikCharlebois NikCharlebois self-assigned this Apr 3, 2023
NikCharlebois added a commit that referenced this issue Apr 3, 2023
Fixes #3117 - IntuneDeviceConfigurationPolicyIOS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Intune
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants