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

Inquiry on Best Practices for Managed Environments and Native Pipelines in Power Platform #9540

Open
tocri opened this issue Jan 27, 2025 · 0 comments

Comments

@tocri
Copy link

tocri commented Jan 27, 2025

Hello Team,

I am reaching out because since I learned about the end of AA4PP, I have started working with managed environments and native PPF pipelines. The work done is top-notch, and the ease of use and setup of the pipelines is truly enjoyable, especially for citizen developers. In short, I really like it.

Now, I would like to get back to basics, because although I would love to deploy managed environments to all my clients, the reality is that this has a cost since a premium Power Apps and/or Power Automate license is required even for consumers. I really wished that a pay-as-you-go approach would be sufficient.

I also have clients who need to create apps that must be accessible to all consumers... and here we're talking about 5,000 consumers.

So, my question is:

How do you manage your environment models? For IT, for example, is it better to stay on unmanaged and they will do deployment with AzDO pipelines? And for citizen devs who want to create apps for their units, would it be better to start with a managed environment and they use the native pipelines?

Previously, I mainly used AA4PP for both IT and Citizen Dev but now, my heart leans towards managed environments which is the future, but also my rational side tells me that money doesn't fall from the sky.

I am very curious to hear about your experiences. (@Jenefer-Monroe @Grant-Archibald-MS )

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

No branches or pull requests

2 participants