You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You've found the GitHub repository that houses the source for the Azure technical documentation that is published on [http://docs.microsoft.com/azure](http://docs.microsoft.com/azure).
4
3
5
-
This repository also contains guidance to help you contribute to our technical documentation. For a list of the articles in the contributors' guide, see [the index](./contributor-guide/contributor-guide-index.md).
4
+
This repository also contains guidance to help you contribute to our technical documentation. For a list of the articles in the contributors' guide, see [the index](contributor-guide/contributor-guide-index.md).
6
5
7
6
## Contribute to Azure documentation
8
-
9
7
Thank you for your interest in Azure documentation!
10
8
11
9
*[Ways to contribute](#ways-to-contribute)
@@ -16,91 +14,74 @@ Thank you for your interest in Azure documentation!
16
14
*[How to use markdown to format your topic](#how-to-use-markdown-to-format-your-topic)
17
15
*[Feedback, comments, and support](./contributor-guide/feedback-and-comments.md)
18
16
*[More resources](#more-resources)
19
-
*[Index of all contributors' guide articles](./contributor-guide/contributor-guide-index.md) (opens new page)
20
-
21
-
## Ways to contribute
17
+
*[Index of all contributors' guide articles](contributor-guide/contributor-guide-index.md) (opens new page)
22
18
19
+
## Ways to contribute
23
20
You can submit updates to the [Azure documentation](http://docs.microsoft.com/azure) as follows:
24
21
25
22
* You can easily contribute to technical articles in the GitHub user interface. Either find the article in this repository, or visit the article on [http://docs.microsoft.com/azur](http://docs.microsoft.com/azur) and click the link in the article that goes to the GitHub source for the article.
26
23
* If you are making substantial changes to an existing article, adding or changing images, or contributing a new article, you need to fork this repository, install Git Bash, Markdown Pad, and learn some git commands.
27
24
28
-
##Code of conduct
29
-
25
+
## Code of conduct
30
26
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
31
27
32
-
##About your contributions to Azure content
33
-
34
-
###Minor corrections
35
-
28
+
## About your contributions to Azure content
29
+
### Minor corrections
36
30
Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the [docs.microsoft.com Terms of Use](https://docs.microsoft.com/en-us/enterprise-mobility-security/termsofuse).
37
31
38
-
39
-
###Larger submissions
40
-
32
+
### Larger submissions
41
33
If you submit a pull request with new or significant changes to documentation and code examples, we'll send a comment in GitHub asking you to submit an online Contribution License Agreement (CLA) if you are not an employee of Microsoft. We need you to complete the online form before we can accept your pull request.
42
34
43
35
## Repository organization
44
-
45
36
The content in the azure-docs repository follows the organization of documentation on http://docs.microsoft.com/azure. This repository contains two root folders:
46
37
47
38
### \articles
48
-
49
39
The *\articles* folder contains the documentation articles formatted as markdown files with an *.md* extension. Articles are typically grouped by Azure service.
50
40
51
-
Articles need to follow strict file naming guidelines - for details, see [our file naming guidance](./contributor-guide/file-names-and-locations.md).
41
+
Articles need to follow strict file naming guidelines - for details, see [our file naming guidance](contributor-guide/file-names-and-locations.md).
52
42
53
43
The *\articles* folder contains the *\media* folder for root directory article media files, inside which are subfolders with the images for each article. The service folders contain a separate media folder for the articles within each service folder. The article image folders are named identically to the article file, minus the *.md* file extension.
54
44
55
45
### \includes
56
-
57
-
You can create reusable content sections to be included in one or more articles. See [Custom extensions used in our technical content](./contributor-guide/custom-markdown-extensions.md).
46
+
You can create reusable content sections to be included in one or more articles. See [Custom extensions used in our technical content](contributor-guide/custom-markdown-extensions.md).
58
47
59
48
### \markdown templates
60
-
61
49
This folder contains our standard markdown template with the basic markdown formatting you need for an article.
62
50
63
51
### \contributor-guide
64
-
65
52
This folder contains articles that are part of our contributors' guide.
66
53
67
54
## Use GitHub, Git, and this repository
55
+
For information about how to contribute, how to use the GitHub UI to contribute small changes, and how to fork and clone the repository for more significant contributions, see [Install and set up tools for authoring in GitHub](contributor-guide/tools-and-setup.md).
68
56
69
-
For information about how to contribute, how to use the GitHub UI to contribute small changes, and how to fork and clone the repository for more significant contributions, see [Install and set up tools for authoring in GitHub](./contributor-guide/tools-and-setup.md).
70
-
71
-
If you install GitBash and choose to work locally, the steps for creating a new local working branch, making changes, and submitting the changes back to the main branch are listed in [Git commands for creating a new article or updating an existing article](./contributor-guide/git-commands-for-master.md)
57
+
If you install GitBash and choose to work locally, the steps for creating a new local working branch, making changes, and submitting the changes back to the main branch are listed in [Git commands for creating a new article or updating an existing article](contributor-guide/git-commands-for-master.md)
72
58
73
59
### Branches
74
-
75
60
We recommend that you create local working branches that target a specific scope of change. Each branch should be limited to a single concept/article both to streamline work flow and reduce the possibility of merge conflicts. The following efforts are of the appropriate scope for a new branch:
76
61
77
62
* A new article (and associated images)
78
63
* Spelling and grammar edits on an article.
79
64
* Applying a single formatting change across a large set of articles (e.g. new copyright footer).
80
65
81
66
## How to use markdown to format your topic
82
-
83
67
All the articles in this repository use GitHub flavored markdown. Here's a list of resources.
Article metadata enables certain functionalities, such as author attribution, contributor attribution, breadcrumbs, article descriptions, and SEO optimizations as well as reporting Microsoft uses to evaluate the performance of the content. So, the metadata is important! [Here's the guidance for making sure your metadata is done right](./contributor-guide/article-metadata.md).
73
+
Article metadata enables certain functionalities, such as author attribution, contributor attribution, breadcrumbs, article descriptions, and SEO optimizations as well as reporting Microsoft uses to evaluate the performance of the content. So, the metadata is important! [Here's the guidance for making sure your metadata is done right](contributor-guide/article-metadata.md).
92
74
93
75
### Labels
94
-
95
76
Automated labels are assigned to pull requests to help us manage the pull request workflow and to help let you know what's going on with your pull request:
96
77
97
78
* Contribution License Agreement related
98
-
* cla-not-required: The change is relatively minor and does not require that you sign a CLA.
99
-
* cla-required: The scope of the change is relatively large and requires that you sign a CLA.
100
-
* cla-signed: The contributor signed the CLA, so the pull request can now move forward for review.
79
+
* cla-not-required: The change is relatively minor and does not require that you sign a CLA.
80
+
* cla-required: The scope of the change is relatively large and requires that you sign a CLA.
81
+
* cla-signed: The contributor signed the CLA, so the pull request can now move forward for review.
101
82
* Pillar labels: Labels such as PnP, Modern Apps, and TDC help categorize the pull requests by the internal organization that needs to review the pull request.
102
83
* Change sent to author: The author has been notified of the pending pull request.
103
84
104
85
## More resources
86
+
See the [index of our contributor's guide](contributor-guide/contributor-guide-index.md) for all our guidance topics.
105
87
106
-
See the [index of our contributor's guide](./contributor-guide/contributor-guide-index.md) for all our guidance topics.
pageTitle="Azure Active Directory B2C: Application registration | Microsoft Azure"
3
-
description="How to register your application with Azure Active Directory B2C"
4
-
services="active-directory-b2c"
5
-
documentationCenter=""
6
-
authors="swkrish"
7
-
manager="mbaldwin"
8
-
editor="bryanla"/>
9
-
10
-
<tags
11
-
ms.service="active-directory-b2c"
12
-
ms.workload="identity"
13
-
ms.tgt_pltfrm="na"
14
-
ms.devlang="na"
15
-
ms.topic="get-started-article"
16
-
ms.date="08/30/2016"
17
-
ms.author="swkrish"/>
18
-
19
-
1
+
---
2
+
title: 'Azure Active Directory B2C: Application registration | Microsoft Docs'
3
+
description: How to register your application with Azure Active Directory B2C
4
+
services: active-directory-b2c
5
+
documentationcenter: ''
6
+
author: swkrish
7
+
manager: mbaldwin
8
+
editor: bryanla
9
+
10
+
ms.service: active-directory-b2c
11
+
ms.workload: identity
12
+
ms.tgt_pltfrm: na
13
+
ms.devlang: na
14
+
ms.topic: get-started-article
15
+
ms.date: 08/30/2016
16
+
ms.author: swkrish
17
+
18
+
---
20
19
# Azure Active Directory B2C: Register your application
21
-
22
20
## Prerequisite
23
-
24
21
To build an application that accepts consumer sign-up and sign-in, you first need to register the application with an Azure Active Directory B2C tenant. Get your own tenant by using the steps outlined in [Create an Azure AD B2C tenant](active-directory-b2c-get-started.md). After you follow all the steps in that article, you will have the B2C features blade pinned to your Startboard.
If you have the B2C features blade pinned to your Startboard, you will see the blade as soon as you sign in to the [Azure portal](https://portal.azure.com/) as the Global Administrator of the B2C tenant.
31
27
32
28
You can also access the blade by clicking **Browse** and then **Azure AD B2C** in the left navigation pane on the [Azure portal](https://portal.azure.com/).
33
29
34
-
> [AZURE.IMPORTANT] You need to be a Global Administrator of the B2C tenant to be able to access the B2C features blade. A Global Administrator from any other tenant or a user from any tenant cannot access it. You can switch to your B2C tenant by using the tenant switcher in the top right corner of the Azure Portal.
30
+
> [!IMPORTANT]
31
+
> You need to be a Global Administrator of the B2C tenant to be able to access the B2C features blade. A Global Administrator from any other tenant or a user from any tenant cannot access it. You can switch to your B2C tenant by using the tenant switcher in the top right corner of the Azure Portal.
32
+
>
33
+
>
35
34
36
35
## Register an application
37
-
38
36
1. On the B2C features blade on the Azure portal, click **Applications**.
39
37
2. Click **+Add** at the top of the blade.
40
38
3. Enter a **Name** for the application that will describe your application to consumers. For example, you could enter "Contoso B2C app".
41
39
4. If you are writing a web-based application, toggle the **Include web app / web API** switch to **Yes**. The **Reply URLs** are endpoints where Azure AD B2C will return any tokens that your application requests. For example, enter `https://localhost:44321/`. If your web application will also be calling some web API secured by Azure AD B2C, you'll want to create an **Application Secret** as well by clicking the **Generate Key** button.
42
-
43
-
> [AZURE.NOTE] An **Application Secret** is an important security credential, and should be secured appropriately.
44
-
40
+
41
+
> [!NOTE]
42
+
> An **Application Secret** is an important security credential, and should be secured appropriately.
43
+
>
44
+
>
45
45
5. If you are writing a mobile application, toggle the **Include native client** switch to **Yes**. Copy down the default **Redirect URI** that is automatically created for you.
46
46
6. Click **Create** to register your application.
47
47
7. Click the application that you just created and copy down the globally unique **Application Client ID** that you'll use later in your code.
48
48
49
-
> [AZURE.IMPORTANT] Applications created in the B2C features blade have to managed in the same location. If you edit B2C applications using PowerShell or another portal, they become unsupported and will likely not work with Azure AD B2C.
49
+
> [!IMPORTANT]
50
+
> Applications created in the B2C features blade have to managed in the same location. If you edit B2C applications using PowerShell or another portal, they become unsupported and will likely not work with Azure AD B2C.
51
+
>
52
+
>
50
53
51
54
## Build a Quick Start Application
52
-
53
55
Now that you have an application registered with Azure AD B2C, you can complete one of our quick-start tutorials to get up and running. Here are a few recommendations:
0 commit comments