Merge branch 'main' into pva-ga-may

Author: Lori Eide

power-platform/admin/database-security.md

@@ -10,7 +10,7 @@ contributors:
 ms.custom: "admin-security"
 ms.component: pa-admin
 ms.topic: conceptual
-ms.date: 04/17/2023
+ms.date: 04/20/2023
 search.audienceType: 
   - admin
 ---
@@ -99,8 +99,8 @@ The following table describes which resources can be authored by each security r
 |---------|---------|---------|---------|---------|
 |Canvas app     |X         |X         |X        |X         |
 |Cloud flow     |X (non-solution aware)         |X         |X (solution aware)         |X         |
-|Connector     |X         |X         |-         |X         |
-|Connection     |X         |X         |-         |X         |
+|Connector     |X (non-solution aware)         |X         |X         |X         |
+|Connection     |X         |X         |X         |X         |
 |Data gateway     |X         |X         |-         |X         |
 |Dataflow     |X         |X         |-         |X         |
 |Dataverse tables     |-         |-         |X         |X         |

power-platform/admin/security-roles-privileges.md

@@ -6,11 +6,8 @@ ms.subservice: admin
 ms.author: paulliew
 ms.reviewer: sericks
 ms.custom: "admin-security"
-ms.component: pa-admin
 ms.topic: conceptual
 ms.date: 04/18/2023
-search.audienceType: 
-  - admin
 ---
 # Security roles and privileges
 
@@ -19,7 +16,7 @@ To control data access, you must set up an organizational structure that both pr
 You can assign security roles using the new, modern UI, or using the the legacy UI:
 
 - [Security roles and the new, modern UI (preview)](security-roles-privileges.md#security-roles-and-the-new-modern-ui-preview)
-- [Security roels and the legacy UI](security-roles-privileges.md#security-roles-and-the-legacy-ui)
+- [Security roles and the legacy UI](security-roles-privileges.md#security-roles-and-the-legacy-ui)
 
 ## Security roles and the new, modern UI (preview)
 > [!Important]

power-platform/guidance/adoption/license-assignment-strategies.md

@@ -3,7 +3,7 @@ title: "License assignment strategies | MicrosoftDocs"
 description: "Guidance for license assignment."
 author: stjeffer
 ms.topic: conceptual
-ms.date: 04/12/2023
+ms.date: 04/20/2023
 ms.subservice: guidance
 ms.author: stjeffer
 ms.reviewer: sericks
@@ -117,4 +117,16 @@ Learn more about on demand license assignment:
 - [Licensing auto-claim for Power Apps](/power-platform/release-plan/2023wave1/power-platform-governance-administration/license-autoclaim-power-apps-licenses)
 - [Auto-claim policies](/microsoft-365/commerce/licenses/manage-auto-claim-policies)
 
+_Request a license_ streamlines the process of assigning licenses for both users and administrators. Whenever a user tries to use a premium Power App without a license, they can easily request one directly from the product.
+
+Administrators can approve or reject numerous requests simultaneously and add a personalized message for their users.
+
+Administrators also have the option to utilize their organization's request process for custom licenses and adjust the relevant settings in the Microsoft 365 admin center.
+
+Learn more about request a license:
+
+- [Request a license (blog)](https://powerapps.microsoft.com/blog/powerapps-request-license/)
+- [Manage self-service license requests](/microsoft-365/commerce/licenses/manage-license-requests?view=o365-worldwide&preserve-view=true)
+- [Request a Power Apps premium license](/power-apps/user/request-license)
+
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

power-platform/guidance/alm-accelerator/branching-environment-strategy.md

@@ -31,7 +31,7 @@ The first time a solution is committed using the ALM Accelerator app, a maker mu
 
 ### Feature Commit Branching
 
-When subsequent features are created by the maker a **new feature branch** should be **created from the solution branch**. The branching strategy is similar ot the initial commit strategy, but the feature branch is created from the solution branch instead of the main branch. In this case the main branch remains unchanged and the solution branch is updated with the latest source code until the solution is ready to be deployed to the production environment again providing a version next branch sometimes referred to as a release branch or v-next branch.
+When subsequent features are created by the maker a **new feature branch** should be **created from the solution branch**. The branching strategy is similar to the initial commit strategy, but the feature branch is created from the solution branch instead of the main branch. In this case the main branch remains unchanged and the solution branch is updated with the latest source code until the solution is ready to be deployed to the production environment again providing a version next branch sometimes referred to as a release branch or v-next branch.
 
 :::image type="content" source="media/almaccelerator-branching/FeatureRun.png" alt-text="Default, feature branch strategy":::