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
Customer usage attribution is a method to associate Azure resources running in customer subscriptions, deployed to run your solution, with you as a partner. Forming these associations in internal Microsoft systems brings greater visibility to the Azure footprint running your software. When you adopt this tracking capability, you align with Microsoft sales teams and gain credit for Microsoft partner programs.
15
15
@@ -41,8 +41,8 @@ We recommend you create a unique GUID for every offer and distribution channel f
41
41
42
42
If you deploy a product by using a template and it is available on both the Azure Marketplace and on GitHub, you can create and register two distinct GUIDS:
43
43
44
-
- Product A in Azure Marketplace
45
-
- Product A on GitHub
44
+
- Product A in Azure Marketplace
45
+
- Product A on GitHub
46
46
47
47
Reporting is done by Microsoft Partner Network ID and GUID.
48
48
@@ -181,53 +181,6 @@ Partners who want to get their deployment via Terraform tracked by customer usag
181
181
* Create a GUID (the GUID should be added for each Offer or SKU)
182
182
* Update their Azure Provider to set the value of *partner_id* to the GUID (DO NOT pre-fix the GUID with "pid-", just set it to the actual GUID)
183
183
184
-
<<<<<<< HEAD
185
-
=======
186
-
## Create GUIDs
187
-
188
-
A GUID is a unique reference number that has 32 hexadecimal digits. To create GUIDs for tracking, you should use a GUID generator. The Azure Storage team has created a [GUID generator form](https://aka.ms/StoragePartners) that will email you a GUID of the correct format and can be reused across the different tracking systems.
189
-
190
-
> [!Note]
191
-
> It is highly recommended that you use [Azure Storage's GUID generator form](https://aka.ms/StoragePartners) to create your GUID. For more information, see our [FAQ](#faq).
192
-
193
-
We recommend you create a unique GUID for every offer and distribution channel for each product. You can opt to use a single GUID for the product's multiple distribution channels if you do not want reporting to be split.
194
-
195
-
If you deploy a product by using a template and it is available on both the Azure Marketplace and on GitHub, you can create and register 2 distinct GUIDS:
196
-
197
-
* Product A in Azure Marketplace
198
-
* Product A on GitHub
199
-
200
-
Reporting is done by the partner value (Microsoft Partner ID) and the GUIDs.
201
-
202
-
You can also track GUIDs at a more granular level like the SKU, where SKUs are variants of an offer.
203
-
204
-
## Register GUIDs and offers
205
-
206
-
The GUIDs must be registered to enable customer usage attribution.
207
-
208
-
All registrations for template GUIDs are done within Partner Center.
209
-
210
-
After you add the GUID to your template or in the user agent, and register the GUID in Partner Center, all deployments are tracked.
211
-
212
-
1. Sign up as a [commercial marketplace publisher](https://aka.ms/JoinMarketplace).
213
-
214
-
* Partners are required to [have a profile in Partner Center](https://docs.microsoft.com/azure/marketplace/become-publisher). You're encouraged to list the offer in the commercial marketplace.
215
-
* Partners can register multiple GUIDs.
216
-
* Partners can register a GUID for the non-Marketplace solution templates and offers.
217
-
218
-
1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard).
219
-
220
-
1. In the upper-right corner, select the settings gear icon, and then select **Developer settings**.
221
-
222
-
1. On the **Account settings page**, select **Add Tracking GUID.**
223
-
224
-
1. In the **GUID** box, enter your tracking GUID. Enter just the GUID without the **pid-** prefix. In the **Description** box, enter your offer name or description.
225
-
226
-
1. To register more than one GUID, select **Add Tracking GUID** again. Additional boxes appear on the page.
227
-
228
-
1. Select **Save**.
229
-
230
-
>>>>>>> master
231
184
232
185
## Verify the GUID deployment
233
186
@@ -317,7 +270,7 @@ If you need assistance for Marketplace Onboarding and/or customer usage attribut
317
270
318
271
1. On the next page, enter the required values.
319
272
320
-
> [!Important]
273
+
> [!IMPORTANT]
321
274
> In the **Incident title** box, enter **ISV Usage Tracking**. Describe your issue in detail.
322
275
323
276

@@ -331,8 +284,7 @@ You can also receive technical guidance from a Microsoft Partner Technical Consu
1. Select Cloud infrastructure and management, and a new page will open for you to view the technical journey.
333
286
1. Under Deployment Services, click the Submit a request button
334
-
1. Sign in using your MSA (MPN account) or your AAD (Partner Dashboard account); based on your
335
-
sign-in credentials, an online request form will open:
287
+
1. Sign in using your MSA (MPN account) or your AAD (Partner Dashboard account); based on your sign-in credentials, an online request form will open:
336
288
* Complete/review the contact information.
337
289
* The consultation details may be pre-populated or select from the drop-downs.
338
290
* Enter a title and the description of the problem (provide as much detail as possible).
@@ -356,11 +308,7 @@ Yes, a customer or implementation partner may customize the template and can cha
356
308
357
309
**Can I track templates deployed from a non-Microsoft repository like GitHub?**
358
310
359
-
<<<<<<< HEAD
360
311
Yes, as long as the GUID is present when the template is deployed, usage is tracked. Partners must still register their GUIDs.
361
-
=======
362
-
Yes, as long as the GUID is present when the template is deployed, usage is tracked. Partners are required to have a profile in the commercial marketplace enrollment in Partner Center to register GUIDs used for the deployment outside of the Azure Marketplace.
0 commit comments