Closed atdheekurteshi closed 2 years ago
This issue was tested with a Microsoft365DSC Version: 1.22.713.1 but still it is not working the same error as described above.
@atdheekurteshi can you please elaborate what the issue is here? The property has been added to 1.22.713.1. Thanks
MOF file is generated but when I use this PowerShell Scripts
Publish-DscConfiguration -Path C:\Users\MOFs\MainConfig -Force -Verbose
Start-DscConfiguration -UseExisting -Force -Verbose -Wait
Output
The following attribute its not a Microsoft365DSC attribute or its not supported.
We cannot replicate the issue on our end and the property is being set properly. Can you make sure the proper version of the module is installed and try removing any older version first
I will try it again and will come with an answer.
The following issue was fixed in Microsoft365DSC Version: 1.22.720.1
ISSUE TITLE:
Add / Include CustomBrowserProtocol Attribute for IntuneAppProtectionPolicyiOS Resource in Microsoft365DSC
ISSUE DESCRIPTION (this template):
IntuneAppProtectionPolicyiOS: Property/Attribute 'CustomBrowserProtocol ' should be added in class IntuneAppProtectionPolicyiOS since in PowerShell is provided
IntuneAppProtectionPolicyiOS Property/Attribute 'CustomBrowserProtocol ' is momentary not supported please could you add it in the IntuneAppProtectionPolicyiOS.
Details of the scenario you tried and the problem that is occurring
Verbose logs showing the problem
Suggested solution to the issue