Skip to content

Commit 427a0ce

Browse files
author
Qian Wen
committed
additional changes from Jonathan
1 parent b91250c commit 427a0ce

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/marketplace/partner-center-portal/create-new-azure-apps-offer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -256,9 +256,9 @@ Add up to 10 Azure subscription IDs manually, or up to 100 if uploading a CSV fi
256256
### Technical configuration
257257

258258
>[!Note]
259-
>Offer-level technical details are optional and only need to be configured if you are publishing a managed app with custom meters authenticating with an Azure AD security token. For more information, see [authentication strategies](./marketplace-metering-service-authentication.md) on the different authentication options.
259+
>Offer-level technical details are optional. You only need to configure these details if you are publishing a managed application with metered billing and have a service which will be authenticating with an Azure AD security token. For more information, see [authentication strategies](./marketplace-metering-service-authentication.md) on the different authentication options.
260260
261-
The **technical configuration** define the technical details (tenant ID, and app ID) used for metered usage, complete this section only if your offer includes a managed application that will emit metering events using the [Marketplace metering service APIs](./marketplace-metering-service-apis.md). Enter the identity that your service will use when emitting metering events.
261+
The technical configuration defines the details (tenant ID, and app ID) used to identity your service, which will emit metering events for a managed application using the [Marketplace metering service APIs](./marketplace-metering-service-apis.md). Enter the identity that your service will use when emitting metering events.
262262

263263
* **Azure AD tenant ID** (required): Inside Azure portal, we require that you [create an Azure Active Directory (AD) app](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal) so that we can validate the connection between our two services is behind an authenticated communication. To find the [tenant ID](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-values-for-signing-in), go to your Azure Active Directory and select **Properties**, then look for the **Directory ID** number listed (for example 50c464d3-4930-494c-963c-1e951d15360e).
264264
* **Azure AD app ID** (required): You also need your [application ID](https://docs.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal#get-values-for-signing-in) and an authentication key. To get those values, go to your Azure Active Directory and select **App registrations**, then look for the **Application ID** number listed (for example 50c464d3-4930-494c-963c-1e951d15360e). To find the authentication key, go to **Settings** and select **Keys**. You will need to provide a description and duration and will then be provided a number value.

0 commit comments

Comments
 (0)