make http call update diagram and TOC

Author: kengaderdus

articles/active-directory-b2c/TOC.yml

@@ -485,7 +485,7 @@
         href: custom-policies-series-branch-in-user-journey.md
       - name: 6 - Validate custom policy files
         href: custom-policies-series-install-xml-extensions.md
-      - name: 7 - Make HTTP call custom policy
+      - name: 7 - Make HTTP call from custom policy
         href: custom-policies-series-call-rest-api.md
         displayName: call rest api, http call, http request
       - name: 8 - Create user record custom policy

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

@@ -22,16 +22,16 @@ Azure Active Directory B2C (Azure AD B2C) custom policy allows you to interact w
 
 In this article, you'll learn how to: 
 
-- Create and deploy a sample Node.js app.
+- Create and deploy a sample Node.js app for use as a RESTful service.
 
-- Make an HTTP call to the Node.js app by using the RESTful technical profile.
+- Make an HTTP call to the Node.js RESTful service by using the RESTful technical profile.
 
-- Handle or report an error that's returned by the Node.js app in your custom policy.
+- Handle or report an error that a RESTful service returns to your custom policy.
 
 
 ## Scenario overview 
 
-In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-in-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real apps don't work this way. If the service, which issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the use must re-enter an access code. 
+In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-in-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the use must re-enter an access code. 
 
 :::image type="content" source="media/custom-policies-series-call-rest-api/screenshot-of-call-rest-api-call.png" alt-text="A flowchart of calling a R E S T  A P I.":::
 
@@ -95,19 +95,19 @@ You need to deploy an app, which will serve as your external app. Your custom po
             }
         });
 
-        app.listen(3000, () => {
-            console.log(`Access code service listening on port !` + 3000);
+        app.listen(80, () => {
+            console.log(`Access code service listening on port !` + 80);
         });
     ```
 
     You can observe that when a user submits a wrong access code, you can return an error directly from the REST API. Custom policies allow you to return an HTTP 4xx error message, such as, 400 (bad request), or 409 (conflict) response status code with a response JSON body formatted as shown in `errorResponse` variable. The source of the accessCode in the app could be read from a database. Learn more about [Returning validation error message](restful-technical-profile.md#returning-validation-error-message).   
 
 1. To test the app works as expected, use the following steps:
-    1. In your terminal, run the `node index.js` command to start your app server on port `3000`. 
+    1. In your terminal, run the `node index.js` command to start your app server on port `80`. 
     1. To make a POST request similar to the one shown below, you can use an HTTP client such as [Microsoft PowerShell](https://learn.microsoft.com/powershell/scripting/overview) or [Postman](https://www.postman.com/):
 
     ```http
-        POST http://localhost:3000/validate-accesscode HTTP/1.1
+        POST http://localhost/validate-accesscode HTTP/1.1
         Host: localhost
         Content-Type: application/x-www-form-urlencoded
     
@@ -118,7 +118,7 @@ You need to deploy an app, which will serve as your external app. Your custom po
 
     ```powershell
         $accessCode="54321"
-        $endpoint="http://localhost:3000/validate-accesscode"
+        $endpoint="http://localhost/validate-accesscode"
         $body=$accessCode
         $response=Invoke-RestMethod -Method Post -Uri $endpoint -Body $body
         echo $response
@@ -146,11 +146,11 @@ For your custom policy to reach your Node.js app, it needs to be reachable, so,
 
 Follow the steps in [Deploy your app to Azure](../app-service/quickstart-nodejs.md#deploy-to-azure) to deploy your Node.js app to Azure. For the **Name** of the app, use a descriptive name such as `custompolicyapi`. Hence:
 
-- App URL looks similar to `https://custompolicyapi.azurewebsites.net:3000`.
+- App URL looks similar to `https://custompolicyapi.azurewebsites.net`.
 
-- Service endpoint looks similar to `https://custompolicyapi.azurewebsites.net:3000/validate-accesscode`.
+- Service endpoint looks similar to `https://custompolicyapi.azurewebsites.net/validate-accesscode`.
 
-You can test the app you've deployed by using an HTTP client such as [Microsoft PowerShell](https://learn.microsoft.com/powershell/scripting/overview) or [Postman](https://www.postman.com/). This time, use `https://custompolicyapi.azurewebsites.net:3000/validate-accesscode` as the endpoint. 
+You can test the app you've deployed by using an HTTP client such as [Microsoft PowerShell](https://learn.microsoft.com/powershell/scripting/overview) or [Postman](https://www.postman.com/). This time, use `https://custompolicyapi.azurewebsites.net/validate-accesscode` as the endpoint. 
 
 ## Step 2 - Call the REST API
 
@@ -159,32 +159,34 @@ Now that your app is running, you need to make an HTTP call from your custom pol
 
 ### Step 2.1 - Define a RESTful Technical profile 
 
-In your `ContosoCustomPolicy.XML` file, locate the `ClaimsProviders` section, and define a new RESTful Technical Profile by using the following code: 
+In your `ContosoCustomPolicy.XML` file, locate the `ClaimsProviders` section, and define a new RESTful technical profile by using the following code: 
 
 ```xml
-    <ClaimsProvider>
-        <DisplayName>HTTP Request Technical Profiles</DisplayName>
-        <TechnicalProfiles>
-            <TechnicalProfile Id="ValidateAccessCodeViaHttp">
-                <DisplayName>Check that the user has entered a valid access code by using Claims Transformations</DisplayName>
-                <Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.RestfulProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
-                <Metadata>
-                    <Item Key="ServiceUrl">https://custompolicyapi.azurewebsites.net:3000/validate-accesscode</Item>
-                    <Item Key="SendClaimsIn">Body</Item>
-                    <Item Key="AuthenticationType">None</Item>
-                    <Item Key="AllowInsecureAuthInProduction">true</Item>
-                </Metadata>
-                <InputClaims>
-                    <InputClaim ClaimTypeReferenceId="accessCode" PartnerClaimType="accessCode" />
-                </InputClaims>
-            </TechnicalProfile>
-        </TechnicalProfiles>
-    </ClaimsProvider>
+    <!--<ClaimsProviders>-->
+        <ClaimsProvider>
+            <DisplayName>HTTP Request Technical Profiles</DisplayName>
+            <TechnicalProfiles>
+                <TechnicalProfile Id="ValidateAccessCodeViaHttp">
+                    <DisplayName>Check that the user has entered a valid access code by using Claims Transformations</DisplayName>
+                    <Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.RestfulProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
+                    <Metadata>
+                        <Item Key="ServiceUrl">https://custompolicyapi.azurewebsites.net/validate-accesscode</Item>
+                        <Item Key="SendClaimsIn">Body</Item>
+                        <Item Key="AuthenticationType">None</Item>
+                        <Item Key="AllowInsecureAuthInProduction">true</Item>
+                    </Metadata>
+                    <InputClaims>
+                        <InputClaim ClaimTypeReferenceId="accessCode" PartnerClaimType="accessCode" />
+                    </InputClaims>
+                </TechnicalProfile>
+            </TechnicalProfiles>
+        </ClaimsProvider>
+    <!--</ClaimsProviders>-->
 ``` 
 
 From the protocol, you can observe that we configure the Technical Profile to use the *RestfulProvider*. You can also observe the following information it the metadata section: 
 
-- The `ServiceUrl` represents the API endpoint. Its value is `https://custompolicyapi.azurewebsites.net:3000/validate-accesscode`. If you deployed your Node.js app using an alternative method, make sure to update the endpoint value.
+- The `ServiceUrl` represents the API endpoint. Its value is `https://custompolicyapi.azurewebsites.net/validate-accesscode`. If you deployed your Node.js app using an alternative method, make sure to update the endpoint value.
 
 - `SendClaimsIn` specifies how the input claims are sent to the RESTful claims provider. Possible values: `Body (default)`, `Form`, `Header`, `Url` or `QueryString`. When you use `Body`, such as in this article, you invoke the *POST* HTTP verb, and the data you send to the API if formatted as key, value pairs in the body of the request. Learn [how to invoke the *GET* HTTP verb, and pass data as query string](restful-technical-profile.md#metadata).  
 
@@ -308,10 +310,4 @@ Next, learn:
 
 - About [RESTful technical profile](restful-technical-profile.md).
 
--  How to [Create a user by using Azure AD B2C custom policy](custom-policies-series-store-user.md)
-
-
-
-
-
-
+-  How to [Create a user by using Azure AD B2C custom policy](custom-policies-series-store-user.md)