Interested in a private company training? Request it here.
This chapter introduces how Environments can used to separate your development, acceptance and production environment. It also explains how you configure environment security so that only approved users can create and manage environments.
Solutions are used by app makers and developers to package related customizations together so that they can be managed and deployed as a single unit. We will see what components can be added to a solution and how they are essentially the building blocks of your environment.
In this chapter you will learn about Connection References and Environment Variables and how they can be used to solve the issue of connecting to separate development/acceptance/production data sources without having to make major changes in a Power Automate Flow or Canvas App.
When developing larger apps and flows it is important to separate your development, acceptance and production environments. In this chapter your will learn how to implement ALM in the Power Platform CLI. You will also see how to unpack Canvas Apps into their source code. From the source code you can reassemble your solutions and import them in your acceptance or production environments.
You do not want your business critical apps and flows to be owned by personal Microsoft 365 account. Likewise, when using the Power Platform CLI to create Deployment Pipelines, you do not want to run them with your Microsoft 365 account. In this chapter you will learn how create and use Service Principals to own and deploy Power Platform artifacts.
Pipelines in the Power Platform aim to democratize application lifecycle management (ALM) for Power Platform and Dynamics 365 customers. They bring ALM automation into the service in a manner that's more approachable for all makers, admins, and developers.
Companies don't move with all their data to the cloud. What if you want to build Canvas Apps or Power Automate Flows that access on-premises data sources? This requires that you install and configure a so-called Data Gateway.
The Microsoft Power Platform CoE Starter Kit is a collection of components and tools that are designed to help you get started with developing a strategy for adopting and supporting the Microsoft Power Platform. In this chapter you will learn how to install and configure the Center of Excellence Toolkit and how it can be used to make sure your organization is following all best practices for the Power Platform.
ALM is the lifecycle management of applications, which includes governance, development, and maintenance. In this course, you will learn how to use the Power Platform features and tools available to manage ALM. By the end of the course, participants will be equipped with a comprehensive skill set for successful development, deployment, and operation of a Power Platform environment.
This course is targeted at Power Platform makers and administrators who are interested in managing and deploying Power Apps and Flows in a corporate environment. Participants should have a basic understanding of Power Apps and Power Automate.