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

Feature Request: Support for Power Platform, Resource Locations in Built-in Policy "[Preview]: Sovereignty Baseline - Global Policies" #895

Open
2 tasks done
KeysAU opened this issue Nov 6, 2024 · 7 comments
Labels
Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required

Comments

@KeysAU
Copy link

KeysAU commented Nov 6, 2024

Describe the feature end to end, including deployment scenario details under which the feature would occur.

The ALZ's "[Preview]: Sovereignty Baseline - Global Policies" does not currently support the Power Platform account type resource location. As it is a built-in policy, you need to create a duplicate definition and modify all existing ALZ policy infrastructure to accommodate your new Definition ID.

This process is unnecessarily complex.

To resolve this, you can either create a new policy definition to include the new regions, request someone at Microsoft to update the built-in policy definition or prompt the Power Platform team to create resources in the appropriate regional locations.

Please update the policy to support the new "microsoft.powerplatform/accounts resource type" regions.
See screenshots below.

Built in screenshot:
Image

Initiative Parameter:
Image

New Location:
Image

Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?

This feature is essential for supporting Power Platform, PowerBI, and Fabric resources without the need to duplicate then customise a built-in policy.

Please provide the correlation id associated with your error or bug.

n/a

Can you describe any alternatives that you have taken since this feature does not exist?

Painstakingly duplicate the built-in policy, then update all repository reference IDs to use the new ID.

Feature Implementation

No response

Check previous GitHub issues

  • I have searched the issues for this item and found no duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@oZakari
Copy link
Contributor

oZakari commented Nov 7, 2024

Hey @Springstone, is there someone from the SLZ team that can help with incorporating the geo-codes in the allowed list for the locations?

@oZakari oZakari added Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required and removed Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required labels Nov 7, 2024
@oZakari
Copy link
Contributor

oZakari commented Nov 13, 2024

Hi @KeysAU, just providing an update that we are working with the team who owns this policy set definition to see if we can get this change incorporated.

@KeysAU
Copy link
Author

KeysAU commented Nov 14, 2024

Amazing! Thank you!

@KeysAU
Copy link
Author

KeysAU commented Nov 28, 2024

Hi @oZakari - any news on this one?

@oZakari
Copy link
Contributor

oZakari commented Dec 3, 2024

Hi @VeronicaSea, does your team have any updates you can share with this one?

cc: @KeysAU

@VeronicaSea
Copy link
Contributor

VeronicaSea commented Dec 3, 2024

Hi @VeronicaSea, does your team have any updates you can share with this one?

cc: @KeysAU

Thanks @oZakari . It is under discussion and will provide you an update.

@KeysAU
Copy link
Author

KeysAU commented Dec 12, 2024

Thanks @VeronicaSea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Policy 📝 Issues / PR's related to Policy Needs: Upstream Policy Changes 🔃 Upstream ESLZ repo policy changes required
Projects
None yet
Development

No branches or pull requests

3 participants