-
Notifications
You must be signed in to change notification settings - Fork 532
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
AADActivityBasedTimeoutPolicy hardcoded Displayname "displayName-value" #5125
Comments
@ssoabx Quickly checked on my computer, and there it is working without any issues. Can you please once again run the following commands:
You might need to tweak the path to match where your file is saved. Did you recompile the configuration after the export? That's necessary for the updated configuration to take place, otherwise it will fall back to the last compiled version (which might contain the wrong value). |
I'll have to check it out a bit later sorry. I just figured I'd report it for now. It applies fine, but it reports as a hardcoded value for the Displayname (check "displayName-value" in the M365dsc code). |
@ssoabx Any news on this? Does it still not work correctly? Maybe update to the latest version 1.24.1106.1? |
There are two occurrences of |
Can't reproduce the issue. Comparing and setting works fine. |
Description of the issue
Seems like the DisplayName got hardcoded for the AADActivityBasedTimeoutPolicy resource. It gets properly found
Policy with Id {34ea2a09-776d-456b-87de-3439c587c77d} and DisplayName {ActivityBasedTimeoutPolicy} was found.
but always reports the DisplayName as displayName-value as the current value.
https://github.com/microsoft/Microsoft365DSC/blob/0048d354b1d18907609361d7a296c178215ec06c/Modules/Microsoft365DSC/DSCResources/MSFT_AADActivityBasedTimeoutPolicy/MSFT_AADActivityBasedTimeoutPolicy.psm1
Microsoft 365 DSC Version
1.24.904.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: