Merge pull request #176511 from dannyevers/57683-pound-sign

v-andreaco · web-flow · commit d7d1f3a94eba · 2021-10-22T17:16:48.000-06:00
Pound sign in URL
diff --git a/articles/marketplace/azure-ad-free-or-trial-landing-page.md b/articles/marketplace/azure-ad-free-or-trial-landing-page.md
@@ -7,7 +7,7 @@ ms.reviewer: dannyevers
 ms.service: marketplace 
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: how-to
-ms.date: 09/04/2020
+ms.date: 10/25/2021
 ---
 
 # Build the landing page for your free or trial SaaS offer in the commercial marketplace
@@ -38,7 +38,9 @@ The following sections in this article will guide you through the process of bui
 
 ## Create an Azure AD app registration
 
-The commercial marketplace is fully integrated with Azure AD. Users arrive at the marketplace authenticated with an [Azure AD account or Microsoft account (MSA)](../active-directory/fundamentals/active-directory-whatis.md#terminology). After acquiring a free or free trial subscription through your list-only offer, the user goes from the commercial marketplace to your landing page URL to activate and manage their subscription to your SaaS application. You must let the user sign in to your application with Azure AD SSO. (The landing page URL is specified in the offer's [Technical configuration](plan-saas-offer.md#technical-information) page.
+The commercial marketplace is fully integrated with Azure AD. Users arrive at the marketplace authenticated with an [Azure AD account or Microsoft account (MSA)](../active-directory/fundamentals/active-directory-whatis.md#terminology). After acquiring a free or free trial subscription through your list-only offer, the user goes from the commercial marketplace to your landing page URL to activate and manage their subscription to your SaaS application. You must let the user sign in to your application with Azure AD SSO. (The landing page URL is specified in the offer's [Technical configuration](plan-saas-offer.md#technical-information) page.)
+
+[!INCLUDE [pound-sign-note](./includes/pound-sign-note.md)]
 
 The first step to using the identity is to make sure your landing page is registered as an Azure AD application. Registering the application lets you use Azure AD to authenticate users and request access to user resources. It can be considered the application's definition, which lets the service know how to issue tokens to the app based on the app's settings.
 
diff --git a/articles/marketplace/azure-ad-transactable-saas-landing-page.md b/articles/marketplace/azure-ad-transactable-saas-landing-page.md
@@ -7,7 +7,7 @@ ms.reviewer: dannyevers
 ms.service: marketplace 
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: how-to
-ms.date: 09/02/2020
+ms.date: 10/25/2021
 ---
 
 # Build the landing page for your transactable SaaS offer in the commercial marketplace
@@ -41,7 +41,9 @@ The following sections will guide you through the process of building a landing
 
 ## Create an Azure AD app registration
 
-The commercial marketplace is fully integrated with Azure AD. Buyers arrive at the marketplace authenticated with an [Azure AD account or Microsoft account (MSA)](../active-directory/fundamentals/active-directory-whatis.md#terminology). After purchase, the buyer goes from the commercial marketplace to your landing page URL to activate and manage their subscription of your SaaS application. You must let the buyer sign in to your application with Azure AD SSO. (The landing page URL is specified in the offer's [Technical configuration](plan-saas-offer.md#technical-information) page.
+The commercial marketplace is fully integrated with Azure AD. Buyers arrive at the marketplace authenticated with an [Azure AD account or Microsoft account (MSA)](../active-directory/fundamentals/active-directory-whatis.md#terminology). After purchase, the buyer goes from the commercial marketplace to your landing page URL to activate and manage their subscription of your SaaS application. You must let the buyer sign in to your application with Azure AD SSO. (The landing page URL is specified in the offer's [Technical configuration](plan-saas-offer.md#technical-information) page.)
+
+[!INCLUDE [pound-sign-note](./includes/pound-sign-note.md)]
 
 The first step to using the identity is to make sure your landing page is registered as an Azure AD application. Registering the application lets you use Azure AD to authenticate users and request access to user resources. It can be considered the application's definition, which lets the service know how to issue tokens to the app based on the app's settings.
 
diff --git a/articles/marketplace/create-new-saas-offer-technical.md b/articles/marketplace/create-new-saas-offer-technical.md
@@ -7,7 +7,7 @@ ms.reviewer: dannyevers
 ms.service: marketplace 
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: how-to
-ms.date: 09/02/2020
+ms.date: 10/25/2021
 ---
 
 # Add technical details for a SaaS offer
@@ -19,17 +19,17 @@ This article describes how to enter technical details that help the Microsoft co
 
 ## Technical configuration
 
-On the **Technical configuration** tab, you'll define the technical details that the commercial marketplace uses to communicate to your SaaS application or solution. 
+On the **Technical configuration** tab, you'll define the technical details that the commercial marketplace uses to communicate to your SaaS application or solution.
 
 - **Landing page URL** (required) – Define the SaaS website URL (for example: `https://contoso.com/signup`) that customers will land on after acquiring your offer from the commercial marketplace and triggering the configuration process from the newly created SaaS subscription.
 
   > [!IMPORTANT]
-  > Your landing page should be up and running 24/7. This is the only way you will be notified about new purchases of your SaaS offers made in the commercial marketplace, or configuration requests of an active subscription of an offer.
+  > Your landing page should be up and running 24/7. This is the only way you will be notified about new purchases of your SaaS offers made in the commercial marketplace, or configuration requests of an active subscription of an offer. Don't include the pound sign character (#) in the landing page URL. Otherwise, customers will not be able to access your landing page.
 
 - **Connection webhook** (required) – For all asynchronous events that Microsoft needs to send to you (for example, SaaS subscription has been canceled), we require you to [provide a connection webhook URL](./partner-center-portal/pc-saas-fulfillment-api-v2.md#implementing-a-webhook-on-the-saas-service). We will call this URL to notify you of the event.
 
   > [!IMPORTANT]
-  > Your webhook should be up and running 24/7 as this is the only way you will be notified about updates about your customers' SaaS subscriptions that are purchased via the comercial marketplace.
+  > Your webhook should be up and running 24/7 as this is the only way you will be notified about updates about your customers' SaaS subscriptions that are purchased via the commercial marketplace.
 
 - **Azure Active Directory tenant ID** (required) – To find the tenant ID for your Azure Active Directory (Azure AD) app, go to the [App registrations](https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) blade in Azure Active Directory. In the **Display name** column, select the app. Then look for the **Directory (tenant) ID** number listed (for example, `50c464d3-4930-494c-963c-1e951d15360e`).
 
@@ -39,4 +39,4 @@ Select **Save draft** before continuing to the next tab: Plan overview.
 
 ## Next steps
 
-- [Create plans for a SaaS offer](create-new-saas-offer-plans.md).
+- [Create plans for a SaaS offer](create-new-saas-offer-plans.md).
diff --git a/articles/marketplace/includes/pound-sign-note.md b/articles/marketplace/includes/pound-sign-note.md
@@ -0,0 +1,13 @@
+---
+title: include file
+description: file
+ms.service: marketplace 
+ms.subservice: partnercenter-marketplace-publisher
+ms.topic: include
+author: dannyevers
+ms.author: mingshen
+ms.date: 10/20/2021
+---
+
+> [!TIP]
+> Don't include the pound sign character (#) in the landing page URL. Otherwise, customers will not be able to access your landing page.
diff --git a/articles/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2.md b/articles/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2.md
@@ -4,7 +4,7 @@ description: Learn how to create and manage a SaaS offer on Microsoft AppSource
 ms.service: marketplace
 ms.subservice: partnercenter-marketplace-publisher
 ms.topic: reference
-ms.date: 10/08/2021
+ms.date: 10/25/2021
 author: saasguide
 ms.author: souchak
 ---
@@ -34,15 +34,17 @@ For account creation to happen:
 
 An example of such call is `https://contoso.com/signup?token=<blob>`, whereas the landing page URL for this SaaS offer in Partner Center is configured as `https://contoso.com/signup`. This token provides the publisher with an ID that uniquely identifies the SaaS purchase and the customer.
 
->[!NOTE]
->The publisher won't be notified of the SaaS purchase until the customer initiates the configuration process from the Microsoft side.
+[!INCLUDE [pound-sign-note](../includes/pound-sign-note.md)]
 
 The landing page URL must be up and running all day, every day, and ready to receive new calls from Microsoft at all times. If the landing page becomes unavailable, customers won't be able to sign up for the SaaS service and start using it.
 
 Next, the publisher must pass the *token* back to Microsoft by calling the [SaaS Resolve API](#resolve-a-purchased-subscription), and entering the token as the value of the `x-ms-marketplace-token header` header parameter. As the result of the Resolve API call, the token is exchanged for details of the SaaS purchase such as unique ID of the purchase, purchased offer ID, and purchased plan ID.
 
 On the landing page, the customer should be signed in to the new or existing SaaS account via Azure Active Directory (Azure AD) single sign-on (SSO).
 
+>[!NOTE]
+>The publisher won't be notified of the SaaS purchase until the customer initiates the configuration process from the Microsoft side.
+
 The publisher should implement SSO to provide the user experience required by Microsoft for this flow. Make sure to use the multitenant Azure AD application and allow both work and school accounts or personal Microsoft accounts when configuring SSO. This requirement applies only to the landing page, for users who are redirected to the SaaS service when already signed in with Microsoft credentials. SSO isn't required for all sign-ins to the SaaS service.
 
 > [!NOTE]
