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
@FabienTschanz When you introduced the caching behaviour to Intune workload you missed that some of those Intune resources still have their get inside Get-TargetResource with "-ErrorAction Stop" which means that if the Id of the resource is not found, I use bogus Ids on purpose in order to test multitenant scenario, the processing of the resource is aborted, this was working before since those gets were inside try/catch blocks and the catch block just assigned $getValue = $null or something equivalent which now it doesn't.
See example of breakage starting on this line here, just check the rest of the get block below it:
I don't have time to see which ones are actually affected by this since I need to go back to a working version to test something else so could you please check this?
Microsoft 365 DSC Version
1.25.122.1
Which workloads are affected
Intune
The DSC configuration
IntuneAppConfigurationPolicy "IntuneAppConfigurationPolicy-IntuneAppConfigurationPolicy_1"
{
ApplicationId =$IntuneApplicationId;
Assignments =@(
MSFT_DeviceManagementConfigurationPolicyAssignments{
deviceAndAppManagementAssignmentFilterType ='none'
groupDisplayName ='DummyGroupExclude'
dataType ='#microsoft.graph.exclusionGroupAssignmentTarget'
groupId ='053dc89a-be83-411a-bad3-909904b7239e'
}
MSFT_DeviceManagementConfigurationPolicyAssignments{
deviceAndAppManagementAssignmentFilterType ='none'
groupDisplayName ='DummyGroupInclude'
dataType ='#microsoft.graph.groupAssignmentTarget'
groupId ='b0b8fd3f-af2a-453b-be57-80182d599f02'
}
);
CertificateThumbprint =$IntuneCertThumbprint;
CustomSettings =@(
MSFT_IntuneAppConfigurationPolicyCustomSetting{
name ='com.microsoft.intune.mam.managedbrowser.AppProxyRedirection'
value ='false'
}
MSFT_IntuneAppConfigurationPolicyCustomSetting{
name ='com.microsoft.intune.mam.managedbrowser.AllowTransitionOnBlock'
value ='true'
}
MSFT_IntuneAppConfigurationPolicyCustomSetting{
name ='com.microsoft.outlook.Contacts.LocalSyncEnabled'
value ='true'
}
MSFT_IntuneAppConfigurationPolicyCustomSetting{
name ='com.microsoft.outlook.Contacts.LocalSyncEnabled.UserChangeAllowed'
value ='true'
}
);
DisplayName ="IntuneAppConfigurationPolicy_1";
Ensure ="Present";
Id ="44754094-9c69-4ee0-b587-d8af4efd4a7e";
TenantId =$OrganizationName;
}
Verbose logs showing the problem
##vso[task.logissue type=error]Deploy execution failed ❌: PowerShell DSC resource MSFT_IntuneAppConfigurationPolicy failed to execute Test-TargetResource functionality with error message: An error occured in Get-TargetResource, the policy {IntuneAppConfigurationPolicy_1} will not be processed. Refer to the event viewer logs for more information.
Environment Information + PowerShell Version
Win11/PS5.1
The text was updated successfully, but these errors were encountered:
Description of the issue
@FabienTschanz When you introduced the caching behaviour to Intune workload you missed that some of those Intune resources still have their get inside
Get-TargetResource
with "-ErrorAction Stop" which means that if the Id of the resource is not found, I use bogus Ids on purpose in order to test multitenant scenario, the processing of the resource is aborted, this was working before since those gets were inside try/catch blocks and the catch block just assigned $getValue = $null or something equivalent which now it doesn't.See example of breakage starting on this line here, just check the rest of the get block below it:
Microsoft365DSC/Modules/Microsoft365DSC/DSCResources/MSFT_IntuneAppConfigurationPolicy/MSFT_IntuneAppConfigurationPolicy.psm1
Line 85 in 3012725
And another here:
Microsoft365DSC/Modules/Microsoft365DSC/DSCResources/MSFT_IntuneApplicationControlPolicyWindows10/MSFT_IntuneApplicationControlPolicyWindows10.psm1
Line 90 in 3012725
I don't have time to see which ones are actually affected by this since I need to go back to a working version to test something else so could you please check this?
Microsoft 365 DSC Version
1.25.122.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
##vso[task.logissue type=error]Deploy execution failed ❌: PowerShell DSC resource MSFT_IntuneAppConfigurationPolicy failed to execute Test-TargetResource functionality with error message: An error occured in Get-TargetResource, the policy {IntuneAppConfigurationPolicy_1} will not be processed. Refer to the event viewer logs for more information.
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: