Solved: Azure Devops Pipeline for Power Platform solution : Tenant to Tenant

Yes, it is possible to move Power Apps solutions and their dependencies across tenants using Azure DevOps Pipelines, but it comes with a few challenges and considerations.

Let me break down your questions and provide solutions and resources.

1. Moving from One Tenant to Another in Azure DevOps Pipeline:

Yes, it's possible to move resources (like Power Apps solutions, flows, and other configurations) from one Azure tenant to another. This is typically done through ALM (Application Lifecycle Management) processes, including the use of Power Platform Build Tools for Azure DevOps.

However, moving between tenants may involve:

Migrating Power Apps solutions (which includes apps, flows, and environment variables).
Handling dependencies like SharePoint lists and other services manually, as they aren’t part of the solution itself.

2. Can Canvas App Solution be Moved Using Azure DevOps Pipelines?

Yes, you can move Canvas App solutions using Azure DevOps Pipelines. To do this, you will need to use Power Platform Build Tools to export and import solutions as part of your CI/CD pipeline.

Steps:

Set up Power Platform Build Tools:
- Install Power Platform Build Tools in your Azure DevOps environment from the Azure DevOps marketplace.
Export Solution from Source Tenant:
- Use the Export Solution task to export your solution, which will include your Canvas App, flows, and other components.
Import Solution into Target Tenant:
- After the solution is exported, use the Import Solution task to import the solution into the destination environment (or tenant).
Handling Dependencies:
- Environment variables: These are part of the solution, but you will need to ensure that environment variables in the target environment are configured with the correct values. You can manage these using environment variable management in the build pipeline or using PowerShell scripts to automate the setup.

3. Handling SharePoint Lists in the Solution:

SharePoint lists are not included directly in Power Apps solutions, so they won’t be automatically moved with the solution. You will need to handle the SharePoint list migration manually or automate the process through PowerShell or other tools.

You can:

Manually create the SharePoint lists in the target environment.
Use PowerShell scripts to export and import SharePoint list data and structure, or use PnP PowerShell to automate this process.

If your Canvas App heavily depends on SharePoint lists, you'll need to ensure that the lists exist and are populated in the target environment before you import your solution.

4. Environment Variables in the Receiver Tenant Using Pipelines:

For environment variables, you’ll need to manage them as part of the pipeline. Here’s how you can handle them:

Create Environment Variables in Target Tenant:
- You can use the Power Platform CLI (PAC CLI) to create and set environment variables in the target tenant.
Export and Import Environment Variables:
- During the export process, environment variables are included in the solution.
- When importing the solution in the target tenant, you’ll need to ensure that environment variables are mapped correctly. You can use environment variable mapping in the Azure DevOps pipeline or manage them manually.
Using Pipeline Variables:
- You can define pipeline variables to handle different values for environment variables between tenants. During the import step, you can reference these pipeline variables to update environment variables.

5. License and Plan for Moving Solutions Every Sprint:

For moving solutions every sprint, you will need to consider the following:

Power Apps Plan: You’ll need a Power Apps Per User Plan or a Power Apps Per App Plan for your users in the target environment. The type of plan depends on how many apps your users need access to.
Azure DevOps: Azure DevOps has different pricing tiers based on the number of users and the type of build pipelines (Free or paid). For CI/CD with Power Platform, you might need the Azure DevOps Pipelines service and possibly a Power Platform Build Tools license.

You can use the Microsoft Power Platform Build Tools for Azure DevOps, which requires the Power Apps (or Power Automate) licenses for the target environment.

For continuous deployment, it’s essential to have DevOps licenses for the build and release pipelines. These are typically part of your Azure DevOps or Microsoft 365 Enterprise plan, but for larger-scale projects, you may need Premium licenses.

6. Relevant Resources & Documentation:

Here are the key resources and steps that can guide you:

Power Platform Build Tools for Azure DevOps:
- Power Platform Build Tools Documentation
- This will guide you in setting up the Azure DevOps pipeline for exporting and importing solutions.
PowerShell Scripts for SharePoint List Migration:
- PnP PowerShell Documentation
- You can automate SharePoint list migrations using this library.
Environment Variables:
- Environment Variables in Solutions
- Learn how to work with environment variables during the solution import/export process.
Power Platform CI/CD Best Practices:
- Application Lifecycle Management (ALM) for Power Apps

7. Video Resources:

Power Platform ALM Overview:
- Power Platform ALM – YouTube
- A YouTube video that covers the basics of ALM (Application Lifecycle Management) in Power Platform.
Azure DevOps for Power Platform:
- CI/CD with Azure DevOps – YouTube
- A video that demonstrates setting up pipelines for Power Platform.

By following these steps and using the relevant tools, you can automate the migration of solutions, environment variables, and even SharePoint lists (with some manual effort or scripts) between tenants, supporting a smooth and efficient process for each sprint.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!