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

Omitting the Ensure property doesn't Create Instance #1738

Closed
NikCharlebois opened this issue Feb 7, 2022 · 1 comment · Fixed by #2143
Closed

Omitting the Ensure property doesn't Create Instance #1738

NikCharlebois opened this issue Feb 7, 2022 · 1 comment · Fixed by #2143

Comments

@NikCharlebois
Copy link
Collaborator

Several resources, when omitting the Ensure parameter do not create the resource's instance. The Ensure parameter should assume "Present" by default when not explicitly mentioned in the configuration.

@andikrueger andikrueger added the Bug Something isn't working label Mar 10, 2022
@andikrueger
Copy link
Collaborator

I was able to identify the following resources that would need the parameter for all methods to be changed from

$Ensure,

to

$Ensure = $true,

List of resources:

  • EXOJournalRule
  • EXOMailTips

@RuudGijsbers I think you own the following ones:

  • IntuneAppConfigurationPolicy
  • IntuneAppProtectionPolicyiOS
  • IntuneDeviceCategory
  • IntuneDeviceCompliancePolicyAndroid
  • IntuneDeviceCompliancePolicyAndroidDeviceOwner
  • IntuneDeviceCompliancePolicyAndroidWorkProfile
  • IntuneDeviceCompliancePolicyiOs
  • IntuneDeviceCompliancePolicyMacOs
  • IntuneDeviceCompliancePolicyWindows10
  • IntuneDeviceConfigurationPolicyAndroidWorkProfile
  • IntuneDeviceConfigurationPolicyiOsWorkProfile
  • IntuneDeviceConfigurationPolicyWindowsWorkProfile
  • IntuneDeviceEnrollmentLimitRestriction
  • IntuneDeviceEnrollmentPlatformRestriction

And obviously we need to update the Module.Template.ps1 file too - this might be the root cause why all Intune resources do not have a default for $Ensure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants