Skip to content

Commit 71d149a

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into quickstarts1
2 parents 398682f + 5ec7be9 commit 71d149a

File tree

431 files changed

+5652
-5815
lines changed

Some content is hidden

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

431 files changed

+5652
-5815
lines changed

.openpublishing.redirection.json

Lines changed: 123 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1758,7 +1758,62 @@
17581758
},
17591759
{
17601760
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-tutorial-analytics.md",
1761-
"redirect_url": "/azure/cognitive-services/custom-decision-service",
1761+
"redirect_url": "/azure/cognitive-services/personalizer",
1762+
"redirect_document_id": false
1763+
},
1764+
{
1765+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-api-reference.md",
1766+
"redirect_url": "/azure/cognitive-services/personalizer",
1767+
"redirect_document_id": false
1768+
},
1769+
{
1770+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-experimentation-reference.md",
1771+
"redirect_url": "/azure/cognitive-services/personalizer",
1772+
"redirect_document_id": false
1773+
},
1774+
{
1775+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-get-started-app.md",
1776+
"redirect_url": "/azure/cognitive-services/personalizer",
1777+
"redirect_document_id": false
1778+
},
1779+
{
1780+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-get-started-browser.md",
1781+
"redirect_url": "/azure/cognitive-services/personalizer",
1782+
"redirect_document_id": false
1783+
},
1784+
{
1785+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-get-started-register.md",
1786+
"redirect_url": "/azure/cognitive-services/personalizer",
1787+
"redirect_document_id": false
1788+
},
1789+
{
1790+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-log-downloader-reference.md",
1791+
"redirect_url": "/azure/cognitive-services/personalizer",
1792+
"redirect_document_id": false
1793+
},
1794+
{
1795+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-overview.md",
1796+
"redirect_url": "/azure/cognitive-services/personalizer",
1797+
"redirect_document_id": false
1798+
},
1799+
{
1800+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-tutorial-ml.md",
1801+
"redirect_url": "/azure/cognitive-services/personalizer",
1802+
"redirect_document_id": false
1803+
},
1804+
{
1805+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-tutorial-news.md",
1806+
"redirect_url": "/azure/cognitive-services/personalizer",
1807+
"redirect_document_id": false
1808+
},
1809+
{
1810+
"source_path": "articles/cognitive-services/custom-decision-service/custom-decision-service-workflow.md",
1811+
"redirect_url": "/azure/cognitive-services/personalizer",
1812+
"redirect_document_id": false
1813+
},
1814+
{
1815+
"source_path": "articles/cognitive-services/custom-decision-service/index.yml",
1816+
"redirect_url": "/azure/cognitive-services/personalizer",
17621817
"redirect_document_id": false
17631818
},
17641819
{
@@ -14720,7 +14775,7 @@
1472014775
{
1472114776
"source_path": "articles/machine-learning/studio/algorithm-choice.md",
1472214777
"redirect_url": "/azure/machine-learning/how-to-select-algorithms",
14723-
"redirect_document_id": false
14778+
"redirect_document_id": true
1472414779
},
1472514780
{
1472614781
"source_path": "articles/machine-learning/machine-learning-algorithm-parameters-optimize.md",
@@ -28441,6 +28496,11 @@
2844128496
"redirect_url": "/azure/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds",
2844228497
"redirect_document_id": false
2844328498
},
28499+
{
28500+
"source_path": "articles/hdinsight/domain-joined/domain-joined-zeppelin-signin.md",
28501+
"redirect_url": "/azure/hdinsight/domain-joined/hdinsight-security-overview",
28502+
"redirect_document_id": false
28503+
},
2844428504
{
2844528505
"source_path": "articles/hdinsight/hdinsight-domain-joined-introduction.md",
2844628506
"redirect_url": "/azure/hdinsight/domain-joined/apache-domain-joined-introduction",
@@ -33803,7 +33863,17 @@
3380333863
},
3380433864
{
3380533865
"source_path": "articles/cognitive-services/entitylinking/index.md",
33806-
"redirect_url": "/azure/cognitive-services/entitylinking/home",
33866+
"redirect_url": "/azure/cognitive-services/text-analytics",
33867+
"redirect_document_id": false
33868+
},
33869+
{
33870+
"source_path": "articles/cognitive-services/entitylinking/GettingStarted.md",
33871+
"redirect_url": "/azure/cognitive-services/text-analytics",
33872+
"redirect_document_id": false
33873+
},
33874+
{
33875+
"source_path": "articles/cognitive-services/entitylinking/Home.md",
33876+
"redirect_url": "/azure/cognitive-services/text-analytics",
3380733877
"redirect_document_id": false
3380833878
},
3380933879
{
@@ -33816,6 +33886,41 @@
3381633886
"redirect_url": "/azure/cognitive-services/LinguisticAnalysisAPI/Home",
3381733887
"redirect_document_id": false
3381833888
},
33889+
{
33890+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/AnalyzeMethod.md",
33891+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33892+
"redirect_document_id": false
33893+
},
33894+
{
33895+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/Analyzer-Names.md",
33896+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33897+
"redirect_document_id": false
33898+
},
33899+
{
33900+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/AnalyzersMethod.md",
33901+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33902+
"redirect_document_id": false
33903+
},
33904+
{
33905+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/Constituency-Parsing.md",
33906+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33907+
"redirect_document_id": false
33908+
},
33909+
{
33910+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/Home.md",
33911+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33912+
"redirect_document_id": false
33913+
},
33914+
{
33915+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/POS-tagging.md",
33916+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33917+
"redirect_document_id": false
33918+
},
33919+
{
33920+
"source_path": "articles/cognitive-services/LinguisticAnalysisAPI/Sentences-and-Tokens.md",
33921+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33922+
"redirect_document_id": false
33923+
},
3381933924
{
3382033925
"source_path": "articles/cognitive-services/Recommendations/index.md",
3382133926
"redirect_url": "/azure/cognitive-services/Recommendations/overview",
@@ -33831,6 +33936,11 @@
3383133936
"redirect_url": "/azure/cognitive-services/Web-Language-Model/Home",
3383233937
"redirect_document_id": false
3383333938
},
33939+
{
33940+
"source_path": "articles/cognitive-services/Web-Language-Model/Home.md",
33941+
"redirect_url": "/azure/machine-learning/studio-module-reference/text-analytics",
33942+
"redirect_document_id": false
33943+
},
3383433944
{
3383533945
"source_path": "articles/data-factory/v1/index.md",
3383633946
"redirect_url": "/azure/data-factory/v1/data-factory-introduction",
@@ -45115,6 +45225,16 @@
4511545225
"redirect_url": "/azure/storage/common/storage-security-guide",
4511645226
"redirect_document_id": false
4511745227
},
45228+
{
45229+
"source_path": "articles/storage/blobs/data-lake-storage-quickstart-create-account.md",
45230+
"redirect_url": "/azure/storage/common/storage-account-create",
45231+
"redirect_document_id": false
45232+
},
45233+
{
45234+
"source_path": "articles/storage/blobs/data-lake-storage-how-to-set-permissions-storage-explorer.md",
45235+
"redirect_url": "/azure/storage/blobs/data-lake-storage-explorer",
45236+
"redirect_document_id": false
45237+
},
4511845238
{
4511945239
"source_path": "articles/security/fundamentals/global-admin.md",
4512045240
"redirect_url": "/azure/active-directory/authentication/multi-factor-authentication",

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In an Azure AD tenant, users that belong to the tenant sign-in with an email add
3535

3636
In an Azure AD B2C tenant, most apps want the user to sign-in with any arbitrary email address (for example, [email protected], [email protected], [email protected], or [email protected]). This type of account is a local account. We also support arbitrary user names as local accounts (for example, joe, bob, sarah, or jim). You can choose one of these two local account types when configuring identity providers for Azure AD B2C in the Azure portal. In your Azure AD B2C tenant, select **Identity providers**, select **Local account**, and then select **Username**.
3737

38-
User accounts for applications must always be created through a sign-up user flow, sign-up or sign-in user flow, or by using the Azure AD Graph API. User accounts created in the Azure portal are only used for administering the tenant.
38+
User accounts for applications can be created through a sign-up user flow, sign-up or sign-in user flow, the Microsoft Graph API, or in the Azure portal.
3939

4040
### Which social identity providers do you support now? Which ones do you plan to support in the future?
4141

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ The **TechnicalProfile** contains the following elements:
9595
| OutputClaimsTransformations | 0:1 | A list of previously defined references to claims transformations that should be executed after the claims are received from the claims provider. |
9696
| ValidationTechnicalProfiles | 0:n | A list of references to other technical profiles that the technical profile uses for validation purposes. For more information, see [validation technical profile](validation-technical-profile.md)|
9797
| SubjectNamingInfo | 0:1 | Controls the production of the subject name in tokens where the subject name is specified separately from claims. For example, OAuth or SAML. |
98-
| IncludeInSso | 0:1 | Whether usage of this technical profile should apply single sign-on (SSO) behavior for the session, or instead require explicit interaction. Possible values: `true` (default), or `false`. |
98+
| IncludeInSso | 0:1 | Whether usage of this technical profile should apply single sign-on (SSO) behavior for the session, or instead require explicit interaction. This element is valid only in SelfAsserted profiles used within a Validation technical profile. Possible values: `true` (default), or `false`. |
9999
| IncludeClaimsFromTechnicalProfile | 0:1 | An identifier of a technical profile from which you want all of the input and output claims to be added to this technical profile. The referenced technical profile must be defined in the same policy file. |
100100
| IncludeTechnicalProfile |0:1 | An identifier of a technical profile from which you want all data to be added to this technical profile. The referenced technical profile must exist in the same policy file. |
101101
| UseTechnicalProfileForSessionManagement | 0:1 | A different technical profile to be used for session management. |

articles/active-directory/authentication/concept-authentication-passwordless.md

Lines changed: 13 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: Azure Active Directory passwordless sign in (preview)
3-
description: Passwordless sign in to Azure AD using FIDO2 security keys or the Microsoft Authenticator app (preview)
3+
description: Learn about options for passwordless sign in to Azure Active Directory using FIDO2 security keys or the Microsoft Authenticator app
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 10/08/2019
9+
ms.date: 01/24/2020
1010

1111
ms.author: iainfou
1212
author: iainfoulds
@@ -17,7 +17,7 @@ ms.collection: M365-identity-device-management
1717
---
1818
# Passwordless authentication options
1919

20-
Multi-factor authentication (MFA) is a great way to secure your organization, but users get frustrated with the additional layer on top of having to remember their passwords. Passwordless authentication methods are more convenient because the password is removed and replaced with something you have plus something you are or something you know.
20+
Multi-factor authentication (MFA) is a great way to secure your organization, but users often get frustrated with the additional security layer on top of having to remember their passwords. Passwordless authentication methods are more convenient because the password is removed and replaced with something you have, plus something you are or something you know.
2121

2222
| | Something you have | Something you are or know |
2323
| --- | --- | --- |
@@ -33,23 +33,23 @@ Each organization has different needs when it comes to authentication. Microsoft
3333

3434
## Windows Hello for Business
3535

36-
Windows Hello for Business is ideal for information workers who have their own designated Windows PC. The biometric and PIN are directly tied to the user's PC, which prevents access from anyone other than the owner. With PKI integration and built-in support for single sign-on (SSO), Windows Hello for Business provides a simple and convenient method for seamlessly accessing corporate resources on-premises and in the cloud.
36+
Windows Hello for Business is ideal for information workers who have their own designated Windows PC. The biometric and PIN are directly tied to the user's PC, which prevents access from anyone other than the owner. With public key infrastructure (PKI) integration and built-in support for single sign-on (SSO), Windows Hello for Business provides a convenient method for seamlessly accessing corporate resources on-premises and in the cloud.
3737

3838
The Windows Hello for Business [planning guide](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-planning-guide) can be used to help you make decisions on the type of Windows Hello for Business deployment and the options you'll need to consider.
3939

4040
## Microsoft Authenticator App
4141

42-
Allow your employees phone to become a passwordless authentication method. You may already be using the Microsoft Authenticator App as a convenient multi-factor authentication option in addition to a password. But now, it’s available as a passwordless option.
42+
Allow your employee's phone to become a passwordless authentication method. You may already be using the Microsoft Authenticator App as a convenient multi-factor authentication option in addition to a password. You can also use the Authenticator App as a passwordless option.
4343

4444
![Sign in to Microsoft Edge with the Microsoft Authenticator app](./media/concept-authentication-passwordless/concept-web-sign-in-microsoft-authenticator-app.png)
4545

46-
It turns any iOS or Android phone into a strong, passwordless credential by allowing users to sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone and then using their biometric (touch or face) or PIN to confirm.
46+
The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm.
4747

4848
## FIDO2 security keys
4949

50-
FIDO2 security keys are an unphishable standards-based passwordless authentication method that can come in any form factor. Fast Identity Online (FIDO) is an open standard for passwordless authentication. It allows users and organizations to leverage the standard to sign in to their resources without a username or password using an external security key or a platform key built into a device.
50+
FIDO2 security keys are an unphishable standards-based passwordless authentication method that can come in any form factor. Fast Identity Online (FIDO) is an open standard for passwordless authentication. FIDO allows users and organizations to leverage the standard to sign in to their resources without a username or password using an external security key or a platform key built into a device.
5151

52-
For public preview, employees can use security keys to sign in to their Azure AD joined Windows 10 devices and get single-sign on to their cloud and on-premises resources. They can also sign in to supported browsers.
52+
For public preview, employees can use security keys to sign in to their Azure AD-joined Windows 10 devices and get single-sign on to their cloud and on-premises resources. Users can also sign in to supported browsers. FIDO2 security keys are a great option for enterprises who are very security sensitive or have scenarios or employees who aren't willing or able to use their phone as a second factor.
5353

5454
![Sign in to Microsoft Edge with a security key](./media/concept-authentication-passwordless/concept-web-sign-in-security-key.png)
5555

@@ -64,7 +64,7 @@ A security key **MUST** implement the following features and extensions from the
6464
| 3 | hmac-secret | This extension ensures you can sign in to your device when it's off-line or in airplane mode. |
6565
| 4 | Multiple accounts per RP | This feature ensures you can use the same security key across multiple services like Microsoft Account and Azure Active Directory. |
6666

67-
The following providers offer FIDO2 security keys of different form factors that are known to be compatible with the passwordless experience. Microsoft encourages customers to evaluate the security properties of these keys by contacting the vendor as well as FIDO Alliance.
67+
The following providers offer FIDO2 security keys of different form factors that are known to be compatible with the passwordless experience. We encourage you to evaluate the security properties of these keys by contacting the vendor as well as FIDO Alliance.
6868

6969
| Provider | Contact |
7070
| --- | --- |
@@ -76,20 +76,18 @@ The following providers offer FIDO2 security keys of different form factors that
7676
| AuthenTrend | [https://authentrend.com/about-us/#pg-35-3](https://authentrend.com/about-us/#pg-35-3) |
7777

7878
> [!NOTE]
79-
> If you purchase and plan to use NFC based security keys you will need a supported NFC reader.
79+
> If you purchase and plan to use NFC-based security keys, you need a supported NFC reader for the security key. The NFC reader isn't an Azure requirement or limitation. Check with the vendor for your NFC-based security key for a list of supported NFC readers.
8080
81-
If you are a vendor and want to get your device on this list, contact [[email protected]](mailto:[email protected]).
82-
83-
FIDO2 security keys are a great option for enterprises who are very security sensitive or have scenarios or employees who aren’t willing or able to use their phone as a second factor.
81+
If you're a vendor and want to get your device on this list of supported devices, contact [[email protected]](mailto:[email protected]).
8482

8583
## What scenarios work with the preview?
8684

8785
- Administrators can enable passwordless authentication methods for their tenant
8886
- Administrators can target all users or select users/groups within their tenant for each method
8987
- End users can register and manage these passwordless authentication methods in their account portal
9088
- End users can sign in with these passwordless authentication methods
91-
- Microsoft Authenticator App: Will work in scenarios where Azure AD authentication is used, including across all browsers, during Windows 10 Out Of Box (OOBE) setup, and with integrated mobile apps on any operating system.
92-
- Security keys: Will work on lock screen for Windows 10 and the web in supported browsers like Microsoft Edge.
89+
- Microsoft Authenticator App: Works in scenarios where Azure AD authentication is used, including across all browsers, during Windows 10 Out Of Box (OOBE) setup, and with integrated mobile apps on any operating system.
90+
- Security keys: Work on lock screen for Windows 10 and the web in supported browsers like Microsoft Edge.
9391

9492
## Next steps
9593

0 commit comments

Comments
 (0)