Skip to content

Commit 37f16c7

Browse files
authored
Merge pull request #112187 from dsindona/json-update
json fix plus brand updates
2 parents 7a91de7 + d5f4f84 commit 37f16c7

File tree

5 files changed

+39
-31
lines changed

5 files changed

+39
-31
lines changed

articles/marketplace/cloud-partner-portal-orig/cloud-partner-portal-lead-management-instructions-https.md

Lines changed: 39 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,41 @@
11
---
2-
title: HTTPS Endpoint | Azure Marketplace
3-
description: Configure lead management for an HTTPS endpoint.
2+
title: Configure lead management using an HTTPS endpoint | Azure Marketplace
3+
description: Learn how to use an HTTP endpoint to handle Microsoft AppSource and Azure Marketplace leads.
44
author: dsindona
55
ms.service: marketplace
66
ms.subservice: partnercenter-marketplace-publisher
77
ms.topic: conceptual
8-
ms.date: 12/24/2018
8+
ms.date: 04/21/2020
99
ms.author: dsindona
1010
---
1111

1212
# Configure lead management using an HTTPS endpoint
1313

14-
You can use an HTTPS endpoint to handle Azure Marketplace and AppSource leads. These leads can be written to that can be written to a Customer Relationship Management (CRM) system or sent out as an email notification. This article describes how to configure lead management using the [Microsoft Flow](https://powerapps.microsoft.com/automate-processes/) automation service.
14+
You can use an HTTPS endpoint to handle Microsoft AppSource and Azure Marketplace leads. These leads can be written to a Customer Relationship Management (CRM) system or sent as an email notification. This article describes how to use the [Microsoft Power Automate](https://powerapps.microsoft.com/automate-processes/) automation service to configure lead management.
1515

16-
## Create a flow using Microsoft Flow
16+
## Create a flow using Microsoft Power Automate
1717

18-
1. Open the [Flow](https://flow.microsoft.com/) webpage. Select **Sign in** or select **Sign up free** to create a free Flow account.
18+
1. Open the [Power Automate](https://flow.microsoft.com/) webpage. Select **Sign in** or select **Sign up free** to create a free Flow account.
1919

20-
2. Sign in and select **My flows** on the menu bar.
20+
1. Sign in and select **My flows** on the menu bar.
21+
> [!div class="mx-imgBorder"]
22+
> ![My flows](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows.png)
2123
22-
![My flows](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows.png)
24+
1. Under **+ New**, select **+ Instant—from blank**.
25+
> [!div class="mx-imgBorder"]
26+
> ![Create from blank](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-create-fromblank.png)
2327
24-
3. Select **+ Create from blank**.
28+
1. Name your flow, and then under **Choose how to trigger this flow**, select **When a HTTP request is received**.
2529

26-
![Create from blank](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-create-fromblank.png)
30+
> [!div class="mx-imgBorder"]
31+
> ![Select the HTTP request received trigger](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-pick-request-trigger.png)
2732
28-
4. Select **Create from blank**.
33+
1. Click the flow step to expand it.
2934

30-
![Create from blank](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-create-fromblank2.png)
35+
> [!div class="mx-imgBorder"]
36+
> ![Expand the flow step](./media/cloud-partner-portal-lead-management-instructions-https/expand-flow-step.png)
3137
32-
5. In the **Search connectors and triggers** field, type "request" to find the Request connector.
33-
6. Under **Triggers**, select **When a HTTP request is received**.
34-
35-
![Select the HTTP request received trigger](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-pick-request-trigger.png)
36-
37-
7. Use one of the following steps to configure the **Request Body JSON Schema**:
38+
1. Use one of the following methods to configure the **Request Body JSON Schema**:
3839

3940
- Copy the [JSON schema](#json-schema) at the end of this article into the **Request Body JSON Schema** text box.
4041
- Select **Use sample payload to generate schema**. In the **Enter or paste a sample JSON payload** text box, paste in the [JSON example](#json-example). Select **Done** to create the schema.
@@ -85,6 +86,7 @@ You can use an HTTPS endpoint to handle Azure Marketplace and AppSource leads. T
8586
![Add an email action](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-configure-email-action.png)
8687

8788
5. Select **Save** to finish your flow.
89+
8890
6. An HTTP POST URL is created in the request. Copy this URL and use it as the HTTPS endpoint.
8991

9092
![HTTP Post URL](./media/cloud-partner-portal-lead-management-instructions-https/https-myflows-get-post-url.png)
@@ -95,7 +97,7 @@ When you configure the lead management information for your offer, select **HTTP
9597

9698
![Add dynamic content](./media/cloud-partner-portal-lead-management-instructions-https/https-image017.png)
9799

98-
When leads are generated, Microsoft sends leads to the Flow, which get routed to the CRM system or email address you configured.
100+
When leads are generated, Microsoft sends leads to your Power Automate flow, which get routed to the CRM system or email address you configured.
99101

100102
## JSON schema and example
101103

@@ -121,6 +123,10 @@ The JSON test example uses the following schema:
121123
"id": "/properties/LeadSource",
122124
"type": "string"
123125
},
126+
"Description": {
127+
"id": "/properties/Description",
128+
"type": "string"
129+
},
124130
"UserDetails": {
125131
"id": "/properties/UserDetails",
126132
"properties": {
@@ -160,23 +166,25 @@ The JSON test example uses the following schema:
160166
}
161167
```
162168

163-
You can copy and edit the following JSON example to use as a test in your MS Flow.
169+
You can copy and edit the following JSON example to use as a test in your flow.
164170

165171
### JSON example
166172

167173
```json
168174
{
169-
"OfferTitle": "Test Microsoft",
170-
"LeadSource": "Test run through MS Flow",
171-
"UserDetails": {
172-
"Company": "Contoso",
173-
"Country": "USA",
174-
"Email": "[email protected]",
175-
"FirstName": "Some",
176-
"LastName": "One",
177-
"Phone": "16175555555",
178-
"Title": "Esquire"
179-
}
175+
"UserDetails": {
176+
"FirstName": "Some",
177+
"LastName": "One",
178+
"Email": "[email protected]",
179+
"Phone": "16175555555",
180+
"Country": "USA",
181+
"Company": "Contoso",
182+
"Title": "Esquire"
183+
},
184+
"LeadSource": "AzureMarketplace",
185+
"ActionCode": "INS",
186+
"OfferTitle": "Test Microsoft",
187+
"Description": "Test run through Power Automate"
180188
}
181189
```
182190

Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)