Skip to content

Commit fc969f2

Browse files
authored
Merge branch 'master' into dataflow-1
2 parents fb88aa5 + d7c469c commit fc969f2

File tree

4,503 files changed

+57931
-35750
lines changed

Some content is hidden

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

4,503 files changed

+57931
-35750
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@
194194
{
195195
"path_to_root": "samples-cognitive-services-speech-sdk",
196196
"url": "https://github.com/Azure-Samples/cognitive-services-speech-sdk",
197-
"branch": "rhurey/quickstart.refactor"
197+
"branch": "release-ignite-cogserv-speech-service"
198198
},
199199
{
200200
"path_to_root": "media-services-v3-dotnet-quickstarts",

.openpublishing.redirection.json

Lines changed: 175 additions & 74 deletions
Large diffs are not rendered by default.

articles/active-directory-b2c/TOC.yml

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,11 @@
7676
items:
7777
- name: App integration
7878
items:
79-
- name: Register an application
79+
- name: Register an OIDC application
8080
href: tutorial-register-applications.md
81+
- name: Register a SAML service provider
82+
href: connect-with-saml-service-providers.md
83+
displayName: SP, RP, service provider, connect
8184
- name: Add a web API application
8285
href: add-web-application.md
8386
- name: Add a native client application
@@ -160,6 +163,9 @@
160163
href: active-directory-b2c-reference-kmsi-custom.md
161164
- name: Password change
162165
href: active-directory-b2c-reference-password-change-custom.md
166+
- name: Phone sign-up & sign-in
167+
href: phone-authentication.md
168+
displayName: otp, passwordless, phone number
163169
- name: UX customization
164170
items:
165171
- name: Configure user input
@@ -168,6 +174,9 @@
168174
href: active-directory-b2c-ui-customization-custom.md
169175
- name: Customize the UI dynamically
170176
href: active-directory-b2c-ui-customization-custom-dynamic.md
177+
- name: Custom email
178+
href: custom-email.md
179+
displayName: verification
171180
- name: Page layout
172181
href: page-layout.md
173182
- name: Enable JavaScript
@@ -196,8 +205,10 @@
196205
items:
197206
- name: ADFS
198207
href: active-directory-b2c-custom-setup-adfs2016-idp.md
208+
displayName: SAML
199209
- name: Salesforce
200210
href: active-directory-b2c-setup-sf-app-custom.md
211+
displayName: SAML
201212
- name: Tokens and session management
202213
items:
203214
- name: Customize tokens
@@ -254,6 +265,8 @@
254265
href: integer-transformations.md
255266
- name: JSON
256267
href: json-transformations.md
268+
- name: Phone number
269+
href: phone-number-claims-transformations.md
257270
- name: External accounts
258271
href: social-transformations.md
259272
- name: StringCollection
@@ -277,6 +290,9 @@
277290
items:
278291
- name: About technical profiles
279292
href: technical-profiles-overview.md
293+
- name: Azure Multi-Factor Authentication
294+
href: multi-factor-auth-technical-profile.md
295+
displayName: mfa
280296
- name: Claim resolvers
281297
href: claim-resolver-overview.md
282298
- name: Azure Active Directory
@@ -289,6 +305,9 @@
289305
href: oauth1-technical-profile.md
290306
- name: OAuth2
291307
href: oauth2-technical-profile.md
308+
- name: One-time password
309+
href: one-time-password-technical-profile.md
310+
displayName: otp
292311
- name: OpenID Connect
293312
href: openid-connect-technical-profile.md
294313
- name: REST
@@ -301,6 +320,11 @@
301320
href: active-directory-b2c-reference-sso-custom.md
302321
- name: Validation
303322
href: validation-technical-profile.md
323+
- name: DisplayControls
324+
href: display-controls.md
325+
items:
326+
- name: Verification
327+
href: display-control-verification.md
304328
- name: UserJourneys
305329
href: userjourneys.md
306330
- name: RelyingParty

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Application types that can be used in Azure Active Directory B2C
2+
title: Application types supported by Azure AD B2C
3+
titleSuffix: Azure AD B2C
34
description: Learn about the types of applications you can use with Azure Active Directory B2C.
45
services: active-directory-b2c
56
author: mmacy

articles/active-directory-b2c/active-directory-b2c-configure-signup-self-asserted-custom.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Add claims and customize user input using custom policies - Azure Active Directory B2C | Microsoft Docs
2+
title: Add claims and customize user input in custom policies
3+
titleSuffix: Azure AD B2C
34
description: Learn how to customize user input and add claims to the sign-up or sign-in journey in Azure Active Directory B2C.
45
services: active-directory-b2c
56
author: mmacy

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Add your own attributes to custom policies in Azure Active Directory B2C | Microsoft Docs
2+
title: Add your own attributes to custom policies
3+
titleSuffix: Azure AD B2C
34
description: A walkthrough on using extension properties and custom attributes and including them in the user interface.
45
services: active-directory-b2c
56
author: mmacy
@@ -297,3 +298,4 @@ For more information on extension properties, see the article [Directory schema
297298
> * 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.
298299
> * Extension attributes in the Graph API are named by using the convention `extension_ApplicationObjectID_attributename`.
299300
> * Custom policies refer to extension attributes as **extension_attributename**. This reference omits the **ApplicationObjectId** in XML.
301+
> * You have to specify the attribute ID in the following format **extension_attributename** wherever it is being referenced.

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
2-
title: Track user behavior by using events in Application Insights from Azure Active Directory B2C | Microsoft Docs
3-
description: Learn how to enable event logs in Application Insights from Azure AD B2C user journeys by using custom policies (preview).
2+
title: Track user behavior with Application Insights
3+
titleSuffix: Azure AD B2C
4+
description: Learn how to enable event logs in Application Insights from Azure AD B2C user journeys by using custom policies.
45
services: active-directory-b2c
56
author: mmacy
67
manager: celestedg
@@ -28,7 +29,7 @@ When you use Azure Active Directory B2C (Azure AD B2C) together with Azure Appli
2829

2930
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.
3031

31-
A technical profile uses this provider to define an event from Azure AD B2C. The profile specifies the name of the event, the claims that are recorded, and the instrumentation key. To post an event, the technical profile is then added as an `orchestration step`, or as a `validation technical profile` in a custom user journey.
32+
A technical profile uses this provider to define an event from Azure AD B2C. The profile specifies the name of the event, the claims that are recorded, and the instrumentation key. To post an event, the technical profile is then added as an `orchestration step` in a custom user journey.
3233

3334
Application Insights can unify the events by using a correlation ID to record a user session. Application Insights makes the event and session available within seconds and presents many visualization, export, and analytical tools.
3435

articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw-secure-basic.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Secure your RESTful services by using HTTP basic authentication in Azure Active Directory B2C | Microsoft Docs
2+
title: Secure a RESTful service by using HTTP basic authentication
3+
titleSuffix: Azure AD B2C
34
description: Secure your custom REST API claims exchanges in your Azure AD B2C by using HTTP basic authentication.
45
services: active-directory-b2c
56
author: mmacy

articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw-secure-cert.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Secure your RESTful service by using client certificates in Azure Active Directory B2C | Microsoft Docs
2+
title: Secure a RESTful service by using client certificates
3+
titleSuffix: Azure AD B2C
34
description: Secure your custom REST API claims exchanges in your Azure AD B2C by using client certificates
45
services: active-directory-b2c
56
author: mmacy

articles/active-directory-b2c/active-directory-b2c-custom-rest-api-netfw.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
title: Integrate REST API claims exchanges in your Azure Active Directory B2C user journey
2+
title: Integrate REST API claims exchanges in a user journey
3+
titleSuffix: Azure AD B2C
34
description: Integrate REST API claims exchanges in your Azure AD B2C user journey as validation of user input.
45
services: active-directory-b2c
56
author: mmacy

0 commit comments

Comments
 (0)