Skip to content

Commit a8a5b4a

Browse files
committed
2 parents 086ad7e + 633e128 commit a8a5b4a

File tree

511 files changed

+6861
-2897
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

511 files changed

+6861
-2897
lines changed

.openpublishing.publish.config.json

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -433,14 +433,6 @@
433433
"master": [
434434
"Publish",
435435
"PDF"
436-
],
437-
"release-event-grid": [
438-
"Publish",
439-
"PDF"
440-
],
441-
"hd-insight-pdf": [
442-
"Publish",
443-
"PDF"
444436
]
445437
},
446438
"need_generate_pdf_url_template": true,

.openpublishing.redirection.json

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -970,6 +970,11 @@
970970
"redirect_url": "/azure/cognitive-services/LUIS/luis-how-to-azure-subscription",
971971
"redirect_document_id": false
972972
},
973+
{
974+
"source_path": "articles/cognitive-services/QnAMaker/Tutorials/create-publish-answer.md",
975+
"redirect_url": "/azure/cognitive-services/QnAMaker/quickstarts/create-new-kb-csharp",
976+
"redirect_document_id": false
977+
},
973978
{
974979
"source_path": "articles/cognitive-services/QnAMaker/Concepts/data-sources-supported.md",
975980
"redirect_url": "/azure/cognitive-services/QnAMaker/concepts/knowledge-base",
@@ -45085,10 +45090,10 @@
4508545090
"redirect_url": "/azure/iot-central/core/howto-use-action-groups/",
4508645091
"redirect_document_id": true
4508745092
},
45088-
{
45089-
"source_path": "articles/storage/blobs/data-lake-storage-use-power-bi.md",
45090-
"redirect_url": "https://docs.microsoft.com/power-query/connectors/datalakestorage",
45091-
"redirect_document_id": false
45093+
{
45094+
"source_path": "articles/storage/blobs/data-lake-storage-use-power-bi.md",
45095+
"redirect_url": "https://docs.microsoft.com/power-query/connectors/datalakestorage",
45096+
"redirect_document_id": false
4509245097
},
4509345098
{
4509445099
"source_path": "articles/iot-central/preview/howto-use-app-templates.md",

articles/active-directory-b2c/azure-monitor.md

Lines changed: 36 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: identity
1111
ms.topic: conceptual
1212
ms.author: marsma
1313
ms.subservice: B2C
14-
ms.date: 02/05/2020
14+
ms.date: 02/10/2020
1515
---
1616

1717
# Monitor Azure AD B2C with Azure Monitor
@@ -20,9 +20,9 @@ Use Azure Monitor to route Azure Active Directory B2C (Azure AD B2C) sign-in and
2020

2121
You can route log events to:
2222

23-
* An Azure storage account.
24-
* An Azure event hub (and integrate with your Splunk and Sumo Logic instances).
25-
* An Azure Log Analytics workspace (to analyze data, create dashboards, and alert on specific events).
23+
* An Azure [storage account](../storage/blobs/storage-blobs-introduction.md).
24+
* An Azure [event hub](../event-hubs/event-hubs-about.md) (and integrate with your Splunk and Sumo Logic instances).
25+
* An [Log Analytics workspace](../azure-monitor/platform/resource-logs-collect-workspace.md) (to analyze data, create dashboards, and alert on specific events).
2626

2727
![Azure Monitor](./media/azure-monitor/azure-monitor-flow.png)
2828

@@ -38,15 +38,15 @@ You can also use the [Azure Cloud Shell](https://shell.azure.com), which include
3838

3939
Azure AD B2C leverages [Azure Active Directory monitoring](../active-directory/reports-monitoring/overview-monitoring.md). To enable *Diagnostic settings* in Azure Active Directory within your Azure AD B2C tenant, you use [delegated resource management](../lighthouse/concepts/azure-delegated-resource-management.md).
4040

41-
You authorize a user in your Azure AD B2C directory (the **Service Provider**) to configure the Azure Monitor instance within the tenant that contains your Azure subscription (the **Customer**). To create the authorization, you deploy an [Azure Resource Manager](../azure-resource-manager/index.yml) template to your Azure AD tenant containing the subscription. The following sections walk you through the process.
41+
You authorize a user or group in your Azure AD B2C directory (the **Service Provider**) to configure the Azure Monitor instance within the tenant that contains your Azure subscription (the **Customer**). To create the authorization, you deploy an [Azure Resource Manager](../azure-resource-manager/index.yml) template to your Azure AD tenant containing the subscription. The following sections walk you through the process.
4242

43-
## Create a resource group
43+
## Create or choose resource group
4444

45-
In the Azure Active Directory (Azure AD) tenant that contains your Azure subscription (*not* the directory that contains your Azure AD B2C tenant), [create a resource group](../azure-resource-manager/management/manage-resource-groups-portal.md#create-resource-groups). Use the following values:
45+
This is the resource group containing the destination Azure storage account, event hub, or Log Analytics workspace to receive data from Azure Monitor. You specify the resource group name when you deploy the Azure Resource Manager template.
4646

47-
* **Subscription**: Select your Azure subscription.
48-
* **Resource group**: Enter name for the resource group. For example, *azure-ad-b2c-monitor*.
49-
* **Region**: Select an Azure location. For example, *Central US*.
47+
[Create a resource group](../azure-resource-manager/management/manage-resource-groups-portal.md#create-resource-groups) or choose an existing one the Azure Active Directory (Azure AD) tenant that contains your Azure subscription, *not* the directory that contains your Azure AD B2C tenant.
48+
49+
This example uses a resource group named *azure-ad-b2c-monitor* in the *Central US* region.
5050

5151
## Delegate resource management
5252

@@ -205,20 +205,42 @@ Once you've deployed the template and have waited a few minutes for the resource
205205

206206
## Configure diagnostic settings
207207

208-
After you've delegated resource management and have selected your subscription, you're ready to [Create diagnostic settings](../active-directory/reports-monitoring/overview-monitoring.md) in the Azure portal.
208+
Diagnostic settings define where logs and metrics for a resource should be sent. Possible destinations are:
209+
210+
- [Azure storage account](../azure-monitor/platform/resource-logs-collect-storage.md)
211+
- [Event hubs](../azure-monitor/platform/resource-logs-stream-event-hubs.md) solutions.
212+
- [Log Analytics workspace](../azure-monitor/platform/resource-logs-collect-workspace.md)
213+
214+
If you haven't already, create an instance of your chosen destination type in the resource group you specified in the [Azure Resource Manager template](#create-an-azure-resource-manager-template).
215+
216+
### Create diagnostic settings
217+
218+
You're ready to [Create diagnostic settings](../active-directory/reports-monitoring/overview-monitoring.md) in the Azure portal.
209219

210220
To configure monitoring settings for Azure AD B2C activity logs:
211221

212222
1. Sign in to the [Azure portal](https://portal.azure.com/).
213223
1. Select the **Directory + Subscription** icon in the portal toolbar, and then select the directory that contains your Azure AD B2C tenant.
214224
1. Select **Azure Active Directory**
215225
1. Under **Monitoring**, select **Diagnostic settings**.
216-
1. Select **+ Add diagnostic setting**.
226+
1. If there are existing settings on the resource, you will see a list of settings already configured. Either select **Add diagnostic setting** to add a new setting, or **Edit** setting to edit an existing one. Each setting can have no more than one of each of the destination types..
217227

218228
![Diagnostics settings pane in Azure portal](./media/azure-monitor/azure-monitor-portal-05-diagnostic-settings-pane-enabled.png)
219229

230+
1. Give your setting a name if it doesn't already have one.
231+
1. Check the box for each destination to send the logs. Select **Configure** to specify their settings as described in the following table.
232+
233+
| Setting | Description |
234+
|:---|:---|
235+
| Archive to a storage account | Name of storage account. |
236+
| Stream to an event hub | The namespace where the event hub is created (if this is your first time streaming logs) or streamed to (if there are already resources that are streaming that log category to this namespace).
237+
| Send to Log Analytics | Name of workspace. |
238+
239+
1. Select **AuditLogs** and **SignInLogs**.
240+
1. Select **Save**.
241+
220242
## Next steps
221243

222-
For more information about adding and configuring diagnostic settings in Azure Monitor, see this tutorial in the Azure Monitor documentation:
244+
For more information about adding and configuring diagnostic settings in Azure Monitor, see [Tutorial: Collect and analyze resource logs from an Azure resource](../azure-monitor/insights/monitor-azure-resource.md).
223245

224-
[Tutorial: Collect and analyze resource logs from an Azure resource](/azure-monitor/learn/tutorial-resource-logs.md)
246+
For information about streaming Azure AD logs to an event hub, see [Tutorial: Stream Azure Active Directory logs to an Azure event hub](../active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md).

articles/active-directory-b2c/custom-policy-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ You need to register these two applications in your Azure AD B2C tenant only onc
6969

7070
### Register the IdentityExperienceFramework application
7171

72-
To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
72+
To register an application in your Azure AD B2C tenant, you can use the **App registrations (Legacy)** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
7373

7474
#### [Applications](#tab/applications/)
7575

articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant-custom.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 09/13/2019
12+
ms.date: 02/10/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -46,6 +46,19 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
4646
1. Select **Certificates & secrets**, and then select **New client secret**.
4747
1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
4848
49+
## Configuring optional claims
50+
51+
If you want to get the `family_name` and `given_name` claims from Azure AD, you can configure optional claims for your application in the Azure portal UI or application manifest. For more information, see [How to provide optional claims to your Azure AD app](../active-directory/develop/active-directory-optional-claims.md).
52+
53+
1. Sign in to the [Azure portal](https://portal.azure.com). Search for and select **Azure Active Directory**.
54+
1. From the **Manage** section, select **App registrations**.
55+
1. Select the application you want to configure optional claims for in the list.
56+
1. From the **Manage** section, select **Token configuration (preview)**.
57+
1. Select **Add optional claim**.
58+
1. Select the token type you want to configure.
59+
1. Select the optional claims to add.
60+
1. Click **Add**.
61+
4962
## Create a policy key
5063
5164
You need to store the application key that you created in your Azure AD B2C tenant.

articles/active-directory-b2c/one-time-password-technical-profile.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 02/03/2020
12+
ms.date: 02/10/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -164,3 +164,10 @@ The following example `TechnicalProfile` is used for verifying a code:
164164
</InputClaims>
165165
</TechnicalProfile>
166166
```
167+
168+
## Next steps
169+
170+
See the following article for example of using one-time password technial profile with custom email verification:
171+
172+
- [Custom email verification in Azure Active Directory B2C](custom-email.md)
173+

articles/active-directory/app-provisioning/index.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
### YamlMime:Landing
22

3-
title: Application provisioning documentation
4-
summary: Azure Active Directory provides secure and seamless access to cloud and on-premises applications. Plus, there's no need to manage passwords. Your end-users can sign in once to access Office 365 and thousands of other applications. Learn how to manage and deploy applications with our quickstarts, tutorials, and guidance.
3+
title: Application and HR provisioning documentation
4+
summary: Azure Active Directory app provisioning lets you automatically create and manage user identities in your cloud (SaaS) apps. Azure AD also offers provisioning with cloud-based human resources (HR) applications. Learn how to manage and deploy cloud app and HR provisioning with our quickstarts, tutorials, and guidance.
55

66
metadata:
77
title: Application provisioning documentation
8-
description: Azure Active Directory provides secure and seamless access to cloud and on-premises applications. Plus, there's no need to manage passwords. Your end-users can sign in once to access Office 365 and thousands of other applications. Learn how to manage and deploy applications with our quickstarts, tutorials, and guidance.
8+
description: Azure Active Directory app provisioning lets you automatically create and manage user identities in your cloud (SaaS) apps. Azure AD also offers provisioning with cloud-based human resources (HR) applications. Learn how to manage and deploy cloud app and HR provisioning with our quickstarts, tutorials, and guidance.
99
ms.service: active-directory
1010
ms.subservice: app-mgmt
1111
ms.workload: identity
1212
ms.topic: landing-page
13-
ms.date: 10/10/2019
13+
ms.date: 02/06/2020
1414
author: msmimart
1515
ms.author: mimart
1616
manager: celested

articles/active-directory/app-provisioning/toc.yml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
1-
- name: Application provisioning documentation
1+
- name: Application and HR provisioning documentation
22
href: index.yml
33
- name: Overview
44
expanded: true
55
items:
66
- name: What is application provisioning?
77
href: user-provisioning.md
88
- name: Tutorials
9-
expanded: true
109
items:
1110
- name: G Suite
1211
href: /azure/active-directory/saas-apps/google-apps-provisioning-tutorial?context=azure/active-directory/app-provisioning/context/app-provisioning-context
@@ -54,8 +53,6 @@
5453
href: check-status-user-account-provisioning.md
5554
- name: Export and import your configuration
5655
href: export-import-provisioning-configuration.md
57-
- name: Build a SCIM endpoint and configure provisioning
58-
href: use-scim-to-provision-users-and-groups.md
5956
- name: Troubleshoot application provisioning
6057
items:
6158
- name: Troubleshoot app provisioning
@@ -74,6 +71,8 @@
7471
href: application-provisioning-when-will-provisioning-finish.md
7572
- name: Provisioning logs
7673
href: /azure/active-directory/reports-monitoring/concept-provisioning-logs?context=azure/active-directory/app-provisioning/context/app-provisioning-context
74+
- name: Build a SCIM endpoint and configure provisioning
75+
href: use-scim-to-provision-users-and-groups.md
7776
- name: Automate configuration using MS Graph
7877
href: application-provisioning-configure-api.md
7978
- name: Reference

0 commit comments

Comments
 (0)