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
Typically, review issues are referenced as pull request (PR). Each PR is linked to an online [Azure DevOps](https://azure.microsoft.com/services/devops/) (previously named Visual Studio Team Services (VSTS)) item, which contains details about the issue. The following image displays an example of the Partner Center experience in case of issues found during reviews.
19
+
Typically, review issues are referenced as pull request (PR). Each PR is linked to an online [Azure DevOps](https://azure.microsoft.com/services/devops/) (previously named Visual Studio Team Services (VSTS)) item, which contains details about the issue. The following image displays an example of the Partner Center experience if issues are found during reviews.
Copy file name to clipboardExpand all lines: articles/marketplace/partner-center-portal/create-new-azure-apps-offer.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,7 +184,7 @@ Provide a short description of your offer (up to 100 characters), which may be u
184
184
185
185
### Long summary
186
186
187
-
Provide a longer description of your offer (up to 256 characters). This may be used in marketplace search results.
187
+
Provide a longer description of your offer (up to 256 characters). The description may be used in marketplace search results.
188
188
189
189
### Description
190
190
@@ -256,14 +256,14 @@ The **Preview** tab enables you to define a limited **Preview Audience** for val
256
256
257
257
Your preview audience is identified by Azure subscription ID GUIDs, paired with an optional description for each. Neither of these fields are visible to customers.
258
258
259
-
Add up to ten Azure subscription IDs manually, or up to 100 if uploading a CSV file. By adding these subscriptions, you are defining an audience that will be allowed preview access to your offer before it is fully published. If your offer is already live, you may still define a preview audience for testing any changes or updates to your offer.
259
+
Add up to 10 Azure subscription IDs manually, or up to 100 if uploading a CSV file. By adding these subscriptions, you are defining an audience that will be allowed preview access to your offer before it is fully published. If your offer is already live, you may still define a preview audience for testing any changes or updates to your offer.
260
260
261
261
>[!Note]
262
262
>The preview audience differs from a private audience. A preview audience is allowed access to your offer *prior* to being published live in the marketplaces. You may also choose to create a plan and make it available only to a private audience (using the plan Availability tab). Your preview audience will be able to see and validate all plans, including plans which will be available only to a private audience once your offer is fully published to the marketplace.
263
263
264
264
## Plan overview
265
265
266
-
The **Plan overview** tab enables you to provide different plan options within the same offer. These plans (referred to as SKUs in the Cloud Partner Portal) can differ in terms of plan type (solution template vs. managed application), monetization, or audience. You must configure at least one plan in order to list your offer in the marketplace.
266
+
The **Plan overview** tab enables you to provide different plan options within the same offer. These plans (referred to as SKUs in the Cloud Partner Portal) can differ in terms of plan type (solution template vs. managed application), monetization, or audience. Configure at least one plan in order to list your offer in the marketplace.
267
267
268
268
Once created, you will see your plan names, IDs, plan type, availability (Public or Private), current publishing status, and any available actions on this tab.
269
269
@@ -308,15 +308,15 @@ Select the **Azure Government Cloud** option to make your solution deployable in
308
308
309
309
This option is only visible if **Azure Government Cloud** is selected under **Cloud availability**.
310
310
311
-
Azure Government services handle data that is subject to certain government regulations and requirements, such as FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. To bring awareness to your certifications for these programs, you can provide up to 100 links describing your certifications. This can be either links to your listing on the program directly, or a links to descriptions of your compliance with them on your own websites. These links will only be visible to Azure Government Cloud customers.
311
+
Azure Government services handle data that is subject to certain government regulations and requirements, such as FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. To bring awareness to your certifications for these programs, you can provide up to 100 links describing your certifications. These links can be either links to your listing on the program directly, or a links to descriptions of your compliance with them on your own websites. These links will only be visible to Azure Government Cloud customers.
312
312
313
313
## Plan listing
314
314
315
315
The **plan listing** tab displays the plan-specific listing information that can be different between different plans for the same offer.
316
316
317
317
### Name
318
318
319
-
Pre-populated based on your name you assigned your plan when you created it. This will appear as the title of this "Software plan" displayed in the marketplace. May contain up to 100 characters.
319
+
Pre-populated based on your name you assigned your plan when you created it. This name will appear as the title of this "Software plan" displayed in the marketplace. May contain up to 100 characters.
320
320
321
321
### Summary
322
322
@@ -345,7 +345,7 @@ You have the option to configure each plan to be visible to everyone or to only
345
345
346
346
### Hide plan
347
347
348
-
If your solution template is intended to be only be deployed indirectly when referenced though another solution template or managed application, check this box to publish your solution template but hide it from customers searching and browsing for it directly.
348
+
If your solution template is intended to be deployed only indirectly when referenced though another solution template or managed application, check this box to publish your solution template but hide it from customers searching and browsing for it directly.
349
349
350
350
## Pricing and availability
351
351
@@ -393,13 +393,13 @@ The **technical configuration** tab allows you to upload the deployment package
393
393
394
394
The **Package details** subtab enables you to edit the draft version of your technical configuration.
395
395
396
-
***Version*** - Assign the current version of the technical configuration. You must increment this version each time you publish a change to this page. Version must be in the format `{integer}.{integer}.{integer}`.
396
+
***Version*** - Assign the current version of the technical configuration. Increment this version each time you publish a change to this page. Version must be in the format `{integer}.{integer}.{integer}`.
397
397
398
398
***Package file*** (`.zip`) - This package contains all of the template files needed for this plan, as well as any additional resources, packaged as a `.zip` file.
399
399
400
400
All Azure application plan packages must include these two files in the root folder of a `.zip` archive:
401
401
402
-
* A Resource Manager template file named [mainTemplate.json](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview). This is the template that automates the deployment of resources into the customers Azure subscription. For examples of ARM templates, see the [Azure Quickstart Templates gallery](https://azure.microsoft.com/documentation/templates/) or the corresponding [GitHub: Azure Resource Manager Quickstart Templates](https://github.com/azure/azure-quickstart-templates) repo.
402
+
* A Resource Manager template file named [mainTemplate.json](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview). This template automates the deployment of resources into the customers Azure subscription. For examples of ARM templates, see the [Azure Quickstart Templates gallery](https://azure.microsoft.com/documentation/templates/) or the corresponding [GitHub: Azure Resource Manager Quickstart Templates](https://github.com/azure/azure-quickstart-templates) repo.
403
403
404
404
* A user interface definition for the Azure application creation experience named [createUiDefinition.json](https://docs.microsoft.com/azure/azure-resource-manager/managed-application-createuidefinition-overview).
405
405
@@ -415,7 +415,7 @@ Managed application plans have additional complexity on the **Technical configur
415
415
416
416
### Enable just-in-time (JIT) access
417
417
418
-
Select this option to enable Just-in-time (JIT) access for this plan. JIT access enables you to request elevated access to a managed application's resources for troubleshooting or maintenance. You always have read-only access to the resources, but for a specific time period you can have greater access. For more information, see [Enable and request just-in-time access for Azure Managed Applications](https://docs.microsoft.com/azure/managed-applications/request-just-in-time-access). To require that consumers of your managed application grant your account permanent access, leave this unchecked.
418
+
Select this option to enable Just-in-time (JIT) access for this plan. JIT access enables you to request elevated access to a managed application's resources for troubleshooting or maintenance. You always have read-only access to the resources, but for a specific time period you can have greater access. For more information, see [Enable and request just-in-time access for Azure Managed Applications](https://docs.microsoft.com/azure/managed-applications/request-just-in-time-access). To require that consumers of your managed application grant your account permanent access, leave this option unchecked.
419
419
420
420
>[!Note]
421
421
>Be sure to update your `createUiDefinition.json` file in order to support this feature.
@@ -439,7 +439,7 @@ Select this option to specify which actions customers can perform on the managed
439
439
440
440
List the additional actions you would like to enable your customer to perform here, separated by semicolons. For more information, see [Understanding deny assignments for Azure resources](https://docs.microsoft.com/azure/role-based-access-control/deny-assignments). For available actions, see [Azure Resource Manager resource provider operations](https://docs.microsoft.com/azure/role-based-access-control/resource-provider-operations). For example, to permit consumers to restart virtual machines, add `Microsoft.Compute/virtualMachines/restart/action` to the allowed actions.
441
441
442
-
### Public Azure / Azure Government Cloud
442
+
### Global Azure / Azure Government Cloud
443
443
444
444
Indicate who should have management access to this managed application in each supported cloud. Users, groups, or applications that you want to be granted permission to the managed resource group are identified using Azure Active Directory (AAD) identities.
445
445
@@ -464,7 +464,7 @@ For more information about completing this tab, see [Co-sell option in Partner C
464
464
465
465
## Test drive
466
466
467
-
The **Test drive** tab enables you to set up a demonstration (or "test drive") which will enable customers to try your offer before committing to purchase it. Learn more in the article [What is Test Drive?](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal/test-drive/what-is-test-drive) If you no longer want to provide a test drive for your offer, return to the **Offer setup** page and un-check**Enable test drive**.
467
+
The **Test drive** tab enables you to set up a demonstration (or "test drive") which will enable customers to try your offer before committing to purchase it. Learn more in the article [What is Test Drive?](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal/test-drive/what-is-test-drive) If you no longer want to provide a test drive for your offer, return to the **Offer setup** page and uncheck**Enable test drive**.
468
468
469
469
### Technical configuration
470
470
@@ -482,7 +482,7 @@ In order to deploy the Test Drive on your behalf, please create and provide a se
482
482
483
483
-**Azure AD app ID** (required): Enter your Azure Active Directory (AD) [application ID](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-values-for-signing-in). To find this ID, sign in to the [Azure portal](https://portal.azure.com/), select the Active Directory tab in the left-menu, select **App registrations**, then look for the **Application ID** number listed (e.g. 50c464d3-4930-494c-963c-1e951d15360e).
484
484
485
-
-**Azure AD app client secret** (required): Enter your Azure AD application [client secret](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#certificates-and-secrets). To find this value, sign in to the [Azure portal](https://portal.azure.com/). Select the **Azure Active Directory** tab in the left menu, select **App registrations**, then select your test drive app. Next, select **Certificates and secrets**, select **New client secret**, enter a description, select **Never** under **Expires**, then choose **Add**. Make sure to copy down the value. (Don't navigate away from the page before you do this, or else you won't have access to the value.)
485
+
-**Azure AD app client secret** (required): Enter your Azure AD application [client secret](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#certificates-and-secrets). To find this value, sign in to the [Azure portal](https://portal.azure.com/). Select the **Azure Active Directory** tab in the left menu, select **App registrations**, then select your test drive app. Next, select **Certificates and secrets**, select **New client secret**, enter a description, select **Never** under **Expires**, then choose **Add**. Make sure to copy down the value. (Don't navigate away from the page before you have copied the value, or else you won't have access to the value.)
486
486
487
487
Remember to **Save** before moving on to the next section!
488
488
@@ -509,7 +509,7 @@ Select **Save** after completing these fields.
509
509
510
510
Once you have completed all the required sections of the offer, select **publish** in the top-right corner of the portal. You will be redirected to the **Review and publish** page.
511
511
512
-
If this is your first time publishing this offer, you can:
512
+
If it is your first time publishing this offer, you can:
513
513
514
514
- See the completion status for each section of the offer.
515
515
-*Not started* - means the section has not been touched and needs to be completed.
0 commit comments