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

PPPowerAppsEnvironment Displayname include Database org id #5508

Closed
sandrola opened this issue Dec 4, 2024 · 0 comments · Fixed by #5517
Closed

PPPowerAppsEnvironment Displayname include Database org id #5508

sandrola opened this issue Dec 4, 2024 · 0 comments · Fixed by #5517

Comments

@sandrola
Copy link
Contributor

sandrola commented Dec 4, 2024

Description of the issue

If a Powerplatform Environment is deployed with ProvisionDatabase = $True the Displayname (readed by Powershell) include the Database orgid. While the DSCResource take this name as Key, it will deploy a new Environment if the name in the configuration is not updated.

Solution:
Change how get-targetResource check the Displayname from -eq to -match.

Cons: Only one Environment can be deployed with the same name.

Microsoft 365 DSC Version

V1.24.1106.3

Which workloads are affected

Power Platform

The DSC configuration

N/A

Verbose logs showing the problem

N/A

Environment Information + PowerShell Version

@ykuijs ykuijs mentioned this issue Dec 10, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant