Skip to content

Commit

Permalink
Live publish for 05 June 2024.
Browse files Browse the repository at this point in the history
  • Loading branch information
bishalgoswami authored Jun 5, 2024
2 parents ef6c3a2 + e052a64 commit 2918e42
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions power-platform/alm/pipelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ author: caburk
ms.subservice: alm
ms.author: matp
ms.custom: ""
ms.date: 02/06/2024
ms.date: 06/05/2024
ms.reviewer: "matp"
ms.topic: "overview"
contributors:
Expand Down Expand Up @@ -107,8 +107,8 @@ A common setup example:

Yes. See [delegated deployments](delegated-deployments-setup.md).

### Can I use different service principals for diffent pipelines and stages?
Yes.
### Can I use different service principals for different pipelines and stages?
Yes. More information: [Deploy with a service principal](delegated-deployments-setup.md#deploy-with-a-service-principal)

### What connections can be used?

Expand Down Expand Up @@ -144,7 +144,7 @@ Yes, together these tools are powerful while keeping maker experiences simple. M

### Can I roll back to a previous version?

Currently, only higher solution versions can be deployed or imported. As a work-around, admins download the artifact from the pipelines host, increment the solution version in the solution.xml file, then manually import it into the target environment.
Yes. If the pipeline setting is enabled, you can [redeploy previous solution versions](redeploy-past-solution-versions.md) from the run history view on the Pipelines page. If the setting is disabled, only higher solution versions can be deployed or imported. As a work-around, admins can download the artifact from the pipelines host, increment the solution version in the solution.xml file, then manually import it into the target environment.

### Can I set retention policies for pipelines data?

Expand All @@ -168,7 +168,7 @@ Navigate to an unmanaged solution in development to an environment associated wi

### Can I deploy across regions?

Not currently. The host and all environments associated with pipelines in a host must be located within the same geographic location (as specified when creating environments). For example, a pipeline can't deploy from Germany to Canada. And a host in Germany shouldn't manage environments in Canada. Instead, separate hosts should be used for Germany and Canada.
Yes, but only if the [Cross-Geo Solution Deployments](enable-cross-geo-solution-deployments.md) setting is enabled in the host. If the setting is disabled, the host and all environments associated with pipelines in a host must be located within the same geographic location (as specified when creating environments). For example, if the setting is disabled, a pipeline can't deploy from Germany to Canada and a host in Germany can't manage environments in Canada. In a case where the tenant administrator would like to prevent cross-geo solution deployments, separate hosts should be used for Germany and Canada.

### Can I deploy the same solution using different pipelines?

Expand Down
2 changes: 1 addition & 1 deletion power-platform/alm/solution-concepts-alm.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ A component represents something that you can potentially customize. Anything th
> ![Components in solution.](media/components-in-solution.png "Components in solution")
> [!NOTE]
> - A solution can be up to 32 MB in size.
> - A solution can be up to 95 MB in size.
> - You can't edit components directly within a managed solution.
To view a list of component types that can be added to any solution, see [ComponentType Options](/powerapps/developer/common-data-service/reference/entities/solutioncomponent#componenttype-options).
Expand Down

0 comments on commit 2918e42

Please sign in to comment.