Merge branch 'master' of https://github.com/mayurigupta13/azure-docs-pr

Author: mayurigupta13

.gitignore

@@ -21,4 +21,4 @@ _themes.VS.Modern/
 articles/directories.txt
 AzureMigration.ps1
 
-!/.vscode/extensions.json
+!/.vscode/extensions.json

.openpublishing.publish.config.json

@@ -74,11 +74,13 @@
       "path_to_root": "policy-templates",
       "url": "https://github.com/Azure/azure-policy",
       "branch": "master",
-      "branch_mapping": {
-        "release-build-mysql": "release-build",
-        "release-build-postgresql": "release-build",
-        "release-build-stellar": "release-build"
-      }
+      "branch_mapping": {}
+    },
+    {
+      "path_to_root": "blueprints-templates",
+      "url": "https://github.com/Azure/azure-blueprints",
+      "branch": "master",
+      "branch_mapping": {}
     },
     {
       "path_to_root": "azure-docs-json-samples",

.openpublishing.redirection.json

@@ -4,7 +4,7 @@ Welcome to the open source [documentation](https://docs.microsoft.com/azure) of
 
 ## Getting Started
 
-Contributing to open source is more than just providing updates, it's also letting us know when there is an issue. Read our [Contributing guidance](.github/CONTRIBUTING.md) to find out more.
+Contributing to open source is more than just providing updates, it's also letting us know when there is an issue. Read our [Contributing guidance](CONTRIBUTING.md) to find out more.
 
 ### Prerequisites
 

README.md

@@ -237,7 +237,7 @@
           href: relyingparty.md
       - name: JavaScript samples
         href: javascript-samples.md
-      - name: Release notes
+      - name: Developer notes
         href: active-directory-b2c-developer-notes-custom.md
       - name: Trust Framework definition
         href: active-directory-b2c-reference-trustframeworks-defined-ief-custom.md
@@ -291,6 +291,8 @@
     items:
     - name: Code samples
       href: https://azure.microsoft.com/resources/samples/?service=active-directory-b2c
+    - name: Cookie definitions
+      href: cookie-definitions.md
     - name: Region availability & data residency
       href: active-directory-b2c-reference-tenant-type.md
     - name: Enable billing

articles/active-directory-b2c/TOC.yml

@@ -104,7 +104,7 @@ To learn how to secure a web API by using Azure AD B2C, check out the web API tu
 
 Applications that are installed on devices, such as mobile and desktop applications, often need to access back-end services or web APIs on behalf of users. You can add customized identity management experiences to your native applications and securely call back-end services by using Azure AD B2C and the [OAuth 2.0 authorization code flow](active-directory-b2c-reference-oauth-code.md).  
 
-In this flow, the application executes [policies](active-directory-b2c-reference-policies.md) and receives an `authorization_code` from Azure AD after the user completes the policy. The `authorization_code` represents the application's permission to call back-end services on behalf of the user who is currently signed in. The application can then exchange the `authorization_code` in the background for an `id_token` and a `refresh_token`.  The application can use the `id_token` to authenticate to a back-end web API in HTTP requests. It can also use the `refresh_token` to get a new `id_token` when an older one expires.
+In this flow, the application executes [policies](active-directory-b2c-reference-policies.md) and receives an `authorization_code` from Azure AD after the user completes the policy. The `authorization_code` represents the application's permission to call back-end services on behalf of the user who is currently signed in. The application can then exchange the `authorization_code` in the background for an `access_token` and a `refresh_token`.  The application can use the `access_token` to authenticate to a back-end web API in HTTP requests. It can also use the `refresh_token` to get a new `access_token` when an older one expires.
 
 ## Current limitations
 

articles/active-directory-b2c/active-directory-b2c-apps.md

@@ -291,7 +291,7 @@ The ID token sent back to your application includes the new extension property a
 
 ## Reference
 
-For more information on extension properties, see the article [Directory schema extensions | Graph API concepts](https://msdn.microsoft.com/Library/Azure/Ad/Graph/howto/azure-ad-graph-api-directory-schema-extensions).
+For more information on extension properties, see the article [Directory schema extensions | Graph API concepts](/previous-versions/azure/ad/graph/howto/azure-ad-graph-api-directory-schema-extensions).
 
 > [!NOTE]
 > * A **TechnicalProfile** is an element type, or function, that defines an endpoint’s name, metadata, and protocol. The **TechnicalProfile** details the exchange of claims that the Identity Experience Framework performs. When this function is called in an orchestration step or from another **TechnicalProfile**, the **InputClaims** and **OutputClaims** are provided as parameters by the caller.  

articles/active-directory-b2c/active-directory-b2c-create-custom-attributes-profile-edit-custom.md

@@ -15,16 +15,15 @@ ms.subservice: B2C
 ---
 # Track user behavior in Azure Active Directory B2C using Application Insights
 
+[!INCLUDE [active-directory-b2c-public-preview](../../includes/active-directory-b2c-public-preview.md)]
+
 When you use Azure Active Directory (Azure AD) B2C together with Azure Application Insights, you can get detailed and customized event logs for your user journeys. In this article, you learn how to:
 
 * Gain insights on user behavior.
 * Troubleshoot your own policies in development or in production.
 * Measure performance.
 * Create notifications from Application Insights.
 
-> [!NOTE]
-> This feature is in preview.
-
 ## How it works
 
 The Identity Experience Framework in Azure AD B2C includes the provider `Handler="Web.TPEngine.Providers.AzureApplicationInsightsProvider, Web.TPEngine, Version=1.0.0.0`. It sends event data directly to Application Insights by using the instrumentation key provided to Azure AD B2C.

articles/active-directory-b2c/active-directory-b2c-custom-guide-eventlogger-appins.md

@@ -12,7 +12,6 @@ ms.date: 09/25/2017
 ms.author: davidmu
 ms.subservice: B2C
 ---
-
 # Secure your RESTful services by using HTTP basic authentication
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
@@ -24,11 +23,13 @@ In this article, you add HTTP basic authentication to your RESTful service so th
 For more information, see [Basic authentication in ASP.NET web API](https://docs.microsoft.com/aspnet/web-api/overview/security/basic-authentication).
 
 ## Prerequisites
+
 Complete the steps in the [Integrate REST API claims exchanges in your Azure AD B2C user journey](active-directory-b2c-custom-rest-api-netfw.md) article.
 
 ## Step 1: Add authentication support
 
 ### Step 1.1: Add application settings to your project's web.config file
+
 1. Open the Visual Studio project that you created earlier.
 
 2. Add the following application settings to the web.config file under the `appSettings` element:
@@ -42,7 +43,7 @@ Complete the steps in the [Integrate REST API claims exchanges in your Azure AD
 
     To generate a complex password, run the following PowerShell code. You can use any arbitrary value.
 
-    ```PowerShell
+    ```powershell
     $bytes = New-Object Byte[] 32
     $rand = [System.Security.Cryptography.RandomNumberGenerator]::Create()
     $rand.GetBytes($bytes)
@@ -51,15 +52,17 @@ Complete the steps in the [Integrate REST API claims exchanges in your Azure AD
     ```
 
 ### Step 1.2: Install OWIN libraries
+
 To begin, add the OWIN middleware NuGet packages to the project by using the Visual Studio Package Manager Console:
 
-```
+```powershell
 PM> Install-Package Microsoft.Owin
 PM> Install-Package Owin
 PM> Install-Package Microsoft.Owin.Host.SystemWeb
 ```
 
 ### Step 1.3: Add an authentication middleware class
+
 Add the `ClientAuthMiddleware.cs` class under the *App_Start* folder. To do so:
 
 1. Right-click the *App_Start* folder, select **Add**, and then select **Class**.
@@ -183,6 +186,7 @@ Add the `ClientAuthMiddleware.cs` class under the *App_Start* folder. To do so:
     ```
 
 ### Step 1.4: Add an OWIN startup class
+
 Add an OWIN startup class named `Startup.cs` to the API. To do so:
 1. Right-click the project, select **Add** > **New Item**, and then search for **OWIN**.
 
@@ -208,17 +212,21 @@ Add an OWIN startup class named `Startup.cs` to the API. To do so:
     ```
 
 ### Step 1.5: Protect the Identity API class
+
 Open Controllers\IdentityController.cs, and add the `[Authorize]` tag to the controller class. This tag restricts access to the controller to users who meet the authorization requirement.
 
 ![Add the Authorize tag to the controller](media/aadb2c-ief-rest-api-netfw-secure-basic/rest-api-netfw-secure-basic-authorize.png)
 
 ## Step 2: Publish to Azure
+
 To publish your project, in Solution Explorer, right-click the **Contoso.AADB2C.API** project, and then select **Publish**.
 
 ## Step 3: Add the RESTful services app ID and app secret to Azure AD B2C
+
 After your RESTful service is protected by the client ID (username) and secret, you must store the credentials in your Azure AD B2C tenant. Your custom policy provides the credentials when it invokes your RESTful services.
 
 ### Step 3.1: Add a RESTful services client ID
+
 1. In your Azure AD B2C tenant, select **B2C Settings** > **Identity Experience Framework**.
 
 
@@ -240,6 +248,7 @@ After your RESTful service is protected by the client ID (username) and secret,
 9. Confirm that you've created the `B2C_1A_B2cRestClientId` key.
 
 ### Step 3.2: Add a RESTful services client secret
+
 1. In your Azure AD B2C tenant, select **B2C Settings** > **Identity Experience Framework**.
 
 2. Select **Policy Keys** to view the keys available in your tenant.
@@ -260,13 +269,15 @@ After your RESTful service is protected by the client ID (username) and secret,
 9. Confirm that you've created the `B2C_1A_B2cRestClientSecret` key.
 
 ## Step 4: Change the technical profile to support basic authentication in your extension policy
+
 1. In your working directory, open the extension policy file (TrustFrameworkExtensions.xml).
 
 2. Search for the `<TechnicalProfile>` node that includes `Id="REST-API-SignUp"`.
 
 3. Locate the `<Metadata>` element.
 
 4. Change the *AuthenticationType* to *Basic*, as follows:
+
     ```xml
     <Item Key="AuthenticationType">Basic</Item>
     ```
@@ -279,6 +290,7 @@ After your RESTful service is protected by the client ID (username) and secret,
         <Key Id="BasicAuthenticationPassword" StorageReferenceId="B2C_1A_B2cRestClientSecret" />
     </CryptographicKeys>
     ```
+
     After you add the snippet, your technical profile should look like the following XML code:
 
     ![Add basic authentication XML elements](media/aadb2c-ief-rest-api-netfw-secure-basic/rest-api-netfw-secure-basic-add-1.png)
@@ -298,6 +310,7 @@ After your RESTful service is protected by the client ID (username) and secret,
 6. Upload the *TrustFrameworkExtensions.xml* file, and then ensure that it passes validation.
 
 ## Step 6: Test the custom policy by using Run Now
+
 1. Open **Azure AD B2C Settings**, and then select **Identity Experience Framework**.
 
     >[!NOTE]
@@ -335,9 +348,10 @@ After your RESTful service is protected by the client ID (username) and secret,
     ```
 
 ## (Optional) Download the complete policy files and code
+
 * After you complete the [Get started with custom policies](active-directory-b2c-get-started-custom.md) walkthrough, we recommend that you build your scenario by using your own custom policy files. For your reference, we have provided [Sample policy files](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/scenarios/aadb2c-ief-rest-api-netfw-secure-basic).
 * You can download the complete code from [Sample Visual Studio solution for reference](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/scenarios/aadb2c-ief-rest-api-netfw/Contoso.AADB2C.API).
 
 ## Next steps
-* [Use client certificates to secure your RESTful API](active-directory-b2c-custom-rest-api-netfw-secure-cert.md)
 
+* [Use client certificates to secure your RESTful API](active-directory-b2c-custom-rest-api-netfw-secure-cert.md)