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
The CIM instance FirewallRules has a property called ProfileTypes which contains where the rules will be applied (notConfigured, domain, public and private and any combination of the last 3) and it should be exported and handled like an array, unfortunately it's being handled like a regular string separated by commas which by itself is not a problem since the API actually expects it that way but the schema.mof file as a ValueMap of these expected values so if you try to compile the blueprint to MOF you get the error below.
Microsoft365DSC\MSFT_MicrosoftGraphwindowsFirewallRule : At least one of the values 'domain,private,public' is not supported or valid for property 'ProfileTypes' on class 'MSFT_MicrosoftGraphWindowsFirewallRule'. Please specify only supported values: notConfigured, domain, private, public.
The proper way to solve this would be to change the property to string array and handle it accordingly in the module, just like it's already being done for InterfaceTypes, but that would be considered a breaking change so the quick fix is to remove the ValueMap from the schema.mof file, I'll raise a PR to fix this.
Microsoft365DSC\MSFT_MicrosoftGraphwindowsFirewallRule : At least one of the values 'domain,private,public' is not supported or valid for property 'ProfileTypes' on class 'MSFT_MicrosoftGraphWindowsFirewallRule'. Please specify only supported values: notConfigured, domain, private, public.
Environment Information + PowerShell Version
Win11 / PS5.1
The text was updated successfully, but these errors were encountered:
Description of the issue
The CIM instance
FirewallRules
has a property called ProfileTypes which contains where the rules will be applied (notConfigured, domain, public and private and any combination of the last 3) and it should be exported and handled like an array, unfortunately it's being handled like a regular string separated by commas which by itself is not a problem since the API actually expects it that way but the schema.mof file as a ValueMap of these expected values so if you try to compile the blueprint to MOF you get the error below.The proper way to solve this would be to change the property to string array and handle it accordingly in the module, just like it's already being done for
InterfaceTypes
, but that would be considered a breaking change so the quick fix is to remove the ValueMap from the schema.mof file, I'll raise a PR to fix this.Microsoft 365 DSC Version
1.24.724.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: