You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
18
18
19
-
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#/).
19
+
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, including:
20
+
21
+
-[Microsoft Low Code Application Development Specialization](https://partner.microsoft.com/partnership/specialization/low-code-application-development)
1.**Initiation** - get service account from your customer
24
28
2.**Registration** - link your access account to your partner ID
25
29
3.**Attribution** - attribute your service account to the Power Platform & Dynamics Customer Insights resources using Solutions
26
30
27
-
We recommend taking these actions in the sequence above.
31
+
We recommend taking these actions in the preceding order.
28
32
29
-
The attribution step is critical and typically happens automatically, as the partner user is the one creating, editing, and updating the resource (i.e. the Power App application, the Power Automate flow, etc.). 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 step #3 above.
33
+
The attribution step is critical and typically happens automatically, as the partner user is the one creating, editing, and updating the resource. For example, the Power App application, the Power Automate flow, and so on. 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 the preceding step #3.
30
34
31
35
> [!NOTE]
32
-
> Solutions are not available for Power BI and Customer Insights. See detailed sections below.
36
+
> Solutions are not available for Power BI and Customer Insights. See the following detailed sections.
33
37
34
-
:::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" :::
38
+
:::image type="content" source="./media/link-partner-id-power-apps-accounts/partner-admin-link-steps.png" alt-text="Diagrams showing the three steps listed previously." border="false" lightbox="./media/link-partner-id-power-apps-accounts/partner-admin-link-steps.png" :::
35
39
36
40
## Initiation - get service account from your customer
37
41
@@ -62,11 +66,11 @@ For more information about using PowerShell or the Azure CLI, see sections under
62
66
63
67
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.
64
68
65
-
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.
69
+
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 assumes ownership of all objects inside the Solution and receive the usage credit.
66
70
67
71
[Attributing the account to Power Platform & Customer Insights resources using Solutions](https://aka.ms/AttributetoResources)
68
72
69
-
The resource and attribute user logic differ for every product and are detailed below.
73
+
The resource and attribute user logic differ for every product.
@@ -77,19 +81,17 @@ The resource and attribute user logic differ for every product and are detailed
77
81
78
82
## Validation
79
83
80
-
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.
81
-
82
-
84
+
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 shows your organization name and Partner ID to represent the account and partner ID were correctly connected.
83
85
84
86
## Alternate approaches
85
87
86
-
The following sections are alternate approaches that you can use to leverage PAL for Power Platform and Customer Insights.
88
+
The following sections are alternate approaches to use PAL for Power Platform and Customer Insights.
87
89
88
-
### Associate PAL with user accounts
90
+
### Associate PAL with user accounts
89
91
90
-
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.
92
+
The Attribution step can also be completed with **user accounts**. Although it's an option, there are some downsides to the approach. For partners with a large number of users, it requires 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 need to manage the users via a spreadsheet.
91
93
92
-
To Associate PAL with User Accounts, follow the same steps as with Service Accounts but do so for each user.
94
+
To Associate PAL with User Accounts, follow the same steps as with Service Accounts but do so for each user.
93
95
94
96
Other points about products:
95
97
@@ -113,7 +115,7 @@ Other points about products:
113
115
114
116
### Tooling to update or change attributed users
115
117
116
-
The following table shows the tooling compatibility to change the owner or co-owner, as described above, **user accounts or dedicated service accounts** after the application has been created.
118
+
The following table shows the tooling compatibility to change the owner or co-owner, as described previously, **user accounts or dedicated service accounts** after the application has been created.
0 commit comments