Merge pull request #226779 from theresapalmer/tpalmer-PAL2

Update PAL doc for Power & CI

Author: v-stsavell

articles/cost-management-billing/manage/link-partner-id-power-apps-accounts.md

@@ -16,13 +16,13 @@ ms.devlang: azurecli
 
 Microsoft partners who are Power Platform and Dynamics 365 Customer Insights service providers work with their customers to manage, configure, and support Power Platform and Customer Insights resources. To get credit for the services, you can associate your partner network ID with the Azure credential used for service delivery that's in your customers’ production environments using the Partner Admin Link (PAL).
 
-PAL allows Microsoft to identify and recognize partners that have Power Platform and Customer Insights customers. Microsoft attributes usage to a partner's organization based on the account's permissions (user role) and scope (tenant, resource, and so on). The attribution is used for Advanced Specializations, such as the [Microsoft Low Code Advanced Specializations](https://partner.microsoft.com/membership/advanced-specialization#tab-content-2), and [Partner Incentives](https://partner.microsoft.com/asset/collection/microsoft-commerce-incentive-resources#/). 
+PAL allows Microsoft to identify and recognize partners that have Power Platform and Customer Insights customers. Microsoft attributes usage to a partner's organization based on the account's permissions (user role) and scope (tenant, resource, and so on). The attribution is used for Specializations, such as the [Microsoft Low Code Advanced Specializations](https://partner.microsoft.com/membership/advanced-specialization#tab-content-2), and [Partner Incentives](https://partner.microsoft.com/asset/collection/microsoft-commerce-incentive-resources#/). 
 
 The following sections explain how to:
 
-1. Get access accounts from your customer
-2. Link your access account to your partner ID
-3. Attribute your access account to the product resource
+1. **Initiation** - get service account from your customer
+2. **Registration** - link your access account to your partner ID
+3. **Attribution** - attribute your service account to the Power Platform & Dynamics Customer Insights resources using Solutions
 
 We recommend taking these actions in the sequence above.
 
@@ -33,38 +33,41 @@ The attribution step is critical and typically happens automatically, as the par
 
 :::image type="content" source="./media/link-partner-id-power-apps-accounts/partner-admin-link-steps.png" alt-text="Images showing the three steps listed above."  border="false" lightbox="./media/link-partner-id-power-apps-accounts/partner-admin-link-steps.png" :::
 
-## Get access accounts from your customer
+## Initiation - get service account from your customer
 
-Before you link your partner ID, your customer must give you access to their Power Platform or Customer Insights resources. They use one of the following options:
+Use a dedicated Service Account for work performed and delivered into production.
 
-* **Directory account** - Your customer can create a dedicated user account, or a user account to act as a service account, in their own directory, and provide access to the product(s) you're working on in production.
-* **Service principal** - Your customer can add an app or script from your organization in their directory and provide access to the product you're working on in production. 
+Through the normal course of business with your customer, determine ownership and access rights of a service account dedicated to you as a partner. 
 
-## Link your access account to your partner ID
+[Creating a Service Account Video](https://aka.ms/ServiceAcct) 
 
-Linking your access account to your partner ID is also called *PAL association*. When you have access to a Production Environment access account, you can use PAL to link the account to your Microsoft partner location ID.
+## Registration - link your access account to your partner ID
 
-For directory accounts (user or service), use the graphical web-based Azure portal, PowerShell, or the Azure CLI to link to your Microsoft partner location ID.
+Perform PAL Association on this Service Account.
 
-For service principal, use PowerShell or the Azure CLI to provide the link your Microsoft partner location ID. Link the partner ID to each customer resource.
+[PAL Association Via Azure portal Video](https://aka.ms/PALAssocAzurePortal)
 
 To use the Azure portal to link to a new partner ID:
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Go to [Link to a partner ID](https://portal.azure.com/#blade/Microsoft_Azure_Billing/managementpartnerblade) in the Azure portal.
+1. Go to [Link to a partner ID](https://portal.azure.com/#blade/Microsoft_Azure_Billing/managementpartnerblade) in the Azure portal.
+2. Sign in to the Azure portal
 3. Enter the [Microsoft Cloud Partner Program](https://partner.microsoft.com/) ID for your organization. Be sure to use the **Associated Partner ID** shown on your partner center profile. It's typically known as your [partner location ID](/partner-center/account-structure).  
     :::image type="content" source="./media/link-partner-id-power-apps-accounts/link-partner-id.png" alt-text="Screenshot showing the Link to a partner ID window." lightbox="./media/link-partner-id-power-apps-accounts/link-partner-id.png" :::
 
 > [!NOTE]
 > To link your partner ID to another customer, switch the directory. Under **Switch directory**, select the appropriate directory.
     
-For more information about using PowerShell or the Azure CLI, see [Use PowerShell, CLI, and other tools](#use-powershell-azure-cli-and-other-tools).
+For more information about using PowerShell or the Azure CLI, see sections under [Alternate approaches](#alternate-approaches).
 
-##  Attribute your access account to product resource
+##  Attribution - attribute your service account to the resource using Solutions
 
-To count the usage of a specific resource, the partner user or guest account needs to be attributed to the *resource* for Power Platform or Dynamics Customer Insights. The access account is the one that you received from your customer. It's the same account that was linked through the Partner Admin Link (PAL).
+To count the usage of a specific resource, the partner service account needs to be attributed to the *resource* for Power Platform or Dynamics Customer Insights. 
 
-To ensure success, we strongly recommend that you use Solutions where available to import your deliverables into the customers Production Environment via a Managed Solution. When you use Solutions, the account used to import the Solution becomes the owner of each deliverable inside the Solution. Linking the account to your partner ID ensures all deliverables inside the Solution are associated to your partner ID, automatically handling this step.
+To ensure success, we strongly recommend that you use [Solutions](/power-apps/maker/data-platform/solutions-overview) where available to import your deliverables into the customers Production Environment via a Managed Solution. Use the Service account to install these Solutions into production environments. The last account with a PAL Association to import the solution will assume ownership of all objects inside the Solution and receive the usage credit. 
+
+[Attributing the account to Power Platform & Customer Insights resources using Solutions](https://aka.ms/AttributetoResources)
+
+The resource and attribute user logic differ for every product and are detailed below. 
 
 | Product | Primary Metric | Resource | Attributed User Logic |
 |---|---|---|---|
@@ -73,6 +76,22 @@ To ensure success, we strongly recommend that you use Solutions where available
 | Power BI | Monthly Active Users (MAU)   | Dataset | The user must be the publisher of the dataset. For more information, see [Publish datasets and reports from Power BI Desktop](/power-bi/create-reports/desktop-upload-desktop-files). In cases of multiple partners being mapped to a single dataset, the user's activity is reviewed to select the *latest* partner. |
 | Customer Insights | Unified Profiles | Instance | Any active user of an Instance is treated as the attributed user. In cases of multiple partners being mapped to a single Instance, the user's activity is reviewed to select the *latest* partner. |
 
+## Validation
+
+The operation of a PAL association is a Boolean operation. Once performed it can be verified visually in the Azure portal or with a PowerShell Command. Either option will show your organization name and Partner ID to represent the account and partner ID were correctly connected. 
+
+
+
+## Alternate approaches
+
+The following sections are alternate approaches that you can use to leverage PAL for Power Platform and Customer Insights. 
+
+### Associate PAL with user accounts 
+
+The Attribution step can also be completed with **user accounts**. While we are including this as an option, there are some downsides to this approach.  For partners with a large number of users, it will require management of user accounts when users are new to the team and/or resign from the team.  If you choose to associate PAL in this way, you will need to manage the users via a spreadsheet.  
+
+To Associate PAL with User Accounts, follow the same steps as with Service Accounts but do so for each user.  
+
 Other points about products:
 
 * **Power Apps - Canvas Applications**
@@ -92,9 +111,6 @@ Other points about products:
   * Make sure the user publishing the report performs the PAL association.
   * Use PowerShell to publish as any user or Service Account.
 
-## Use PowerShell, Azure CLI, and other tools
-
-The following sections cover PowerShell, Azure CLI, and other tools to manage ownership and link partner IDs.
 
 ### Tooling to update or change attributed users