Skip to content

Commit edeca2d

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into digital-twins-tutorials
2 parents 99c61e0 + e8af69c commit edeca2d

File tree

133 files changed

+3082
-1476
lines changed

Some content is hidden

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

133 files changed

+3082
-1476
lines changed

.openpublishing.redirection.json

Lines changed: 41 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3308,7 +3308,7 @@
33083308
},
33093309
{
33103310
"source_path": "articles/application-insights/enable-profiler-compute.md",
3311-
"redirect_url": "/azure/application-insights/app-insights-overview",
3311+
"redirect_url": "/azure/application-insights/app-insights-profiler-overview",
33123312
"redirect_document_id": false
33133313
},
33143314
{
@@ -27642,6 +27642,31 @@
2764227642
"redirect_url": "/azure/iot-accelerators/quickstart-device-simulation-deploy",
2764327643
"redirect_document_id": false
2764427644
},
27645+
{
27646+
"source_path": "articles/iot-accelerators/iot-accelerators-device-simulation-create-simulated-device.md",
27647+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-device-simulation-advanced-device",
27648+
"redirect_document_id": false
27649+
},
27650+
{
27651+
"source_path": "articles/iot-accelerators/iot-accelerators-device-simulation-deploy-simulated-device.md",
27652+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-device-simulation-advanced-device",
27653+
"redirect_document_id": false
27654+
},
27655+
{
27656+
"source_path": "articles/iot-accelerators/iot-accelerators-device-simulation-custom-model.md",
27657+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-device-simulation-create-custom-device",
27658+
"redirect_document_id": false
27659+
},
27660+
{
27661+
"source_path": "articles/iot-accelerators/iot-accelerators-device-simulation-device-schema.md",
27662+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-device-simulation-advanced-device",
27663+
"redirect_document_id": false
27664+
},
27665+
{
27666+
"source_path": "articles/iot-accelerators/iot-accelerators-device-simulation-device-behavior.md",
27667+
"redirect_url": "/azure/iot-accelerators/iot-accelerators-device-simulation-advanced-device",
27668+
"redirect_document_id": false
27669+
},
2764527670
{
2764627671
"source_path": "articles/active-directory/develop/active-directory-v2-devquickstarts-angular-dotnet.md",
2764727672
"redirect_url": "/azure/active-directory/develop/GuidedSetups/active-directory-javascriptspa",
@@ -29158,6 +29183,21 @@
2915829183
"redirect_url": "/azure/active-directory-b2c/active-directory-b2c-tutorials-spa",
2915929184
"redirect_document_id": true
2916029185
},
29186+
{
29187+
"source_path": "articles/active-directory-b2c/active-directory-b2c-language-customization-custom.md",
29188+
"redirect_url": "/azure/active-directory-b2c/localization",
29189+
"redirect_document_id": true
29190+
},
29191+
{
29192+
"source_path": "articles/active-directory-b2c/active-directory-b2c-reference-ui-customization.md",
29193+
"redirect_url": "/azure/active-directory-b2c/customize-ui-overview",
29194+
"redirect_document_id": true
29195+
},
29196+
{
29197+
"source_path": "articles/active-directory-b2c/active-directory-b2c-reference-ui-customization-helper-tool.md",
29198+
"redirect_url": "/azure/active-directory-b2c/tutorial-customize-ui",
29199+
"redirect_document_id": true
29200+
},
2916129201
{
2916229202
"source_path": "articles/cognitive-services/video-indexer/video-indexer-output-json.md",
2916329203
"redirect_url": "/azure/cognitive-services/video-indexer/video-indexer-output-json-v2",

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: mtillman
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 08/16/2017
11+
ms.date: 11/01/2018
1212
ms.author: davidmu
1313
ms.component: B2C
1414
---
@@ -76,7 +76,7 @@ Currently there is no way to change the "From:" field on the email. Vote on [fee
7676
You can use the Azure AD Graph API to write your migration tool. See the [User migration guide](active-directory-b2c-user-migration.md) for details.
7777

7878
### What password policy is used for local accounts in Azure AD B2C?
79-
The Azure AD B2C password policy for local accounts is based on the policy for Azure AD. Azure AD B2C's sign-up, sign-up or sign-in and password reset policies uses the "strong" password strength and doesn't expire any passwords. Read the [Azure AD password policy](https://msdn.microsoft.com/library/azure/jj943764.aspx) for more details.
79+
The Azure AD B2C password policy for local accounts is based on the policy for Azure AD. Azure AD B2C's sign-up, sign-up or sign-in and password reset policies uses the "strong" password strength and doesn't expire any passwords. Read the [Azure AD password policy](https://msdn.microsoft.com/library/azure/jj943764.aspx) for more details. For information about account lockouts and passwords, see [Manages threats to resources and data in Azure Active Directory B2C](active-directory-b2c-reference-threat-management.md).
8080

8181
### Can I use Azure AD Connect to migrate consumer identities that are stored on my on-premises Active Directory to Azure AD B2C?
8282
No, Azure AD Connect is not designed to work with Azure AD B2C. Consider using the [Graph API](active-directory-b2c-devquickstarts-graph-dotnet.md) for user migration. See the [User migration guide](active-directory-b2c-user-migration.md) for details.

articles/active-directory-b2c/active-directory-b2c-language-customization-custom.md

Lines changed: 0 additions & 94 deletions
This file was deleted.
Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Threat management in Azure Active Directory B2C | Microsoft Docs
2+
title: Manage threats to resources and data in Azure Active Directory B2C | Microsoft Docs
33
description: Learn about detection and mitigation techniques for denial-of-service attacks and password attacks in Azure Active Directory B2C.
44
services: active-directory-b2c
55
author: davidmu1
@@ -8,20 +8,30 @@ manager: mtillman
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 03/27/2016
11+
ms.date: 11/01/2018
1212
ms.author: davidmu
1313
ms.component: B2C
1414
---
15-
# Azure Active Directory B2C: Threat management
15+
# Manage threats to resources and data in Azure Active Directory B2C
1616

17-
Threat management includes planning for protection from attacks against your system and networks. Denial-of-service attacks might make resources unavailable to intended users. Password attacks lead to unauthorized access to resources. Azure Active Directory B2C (Azure AD B2C) has built-in features that can help you protect your data against these threats in multiple ways.
17+
Azure Active Directory (Azure AD) B2C has built-in features that can help you protect against threats to your resources and data. These threats include denial-of-service attacks and password attacks. Denial-of-service attacks might make resources unavailable to intended users. Password attacks lead to unauthorized access to resources.
1818

1919
## Denial-of-service attacks
2020

21-
Azure AD B2C uses detection and mitigation techniques like SYN cookies, and rate and connection limits to protect underlying resources against denial-of-service attacks.
21+
Azure AD B2C defends against SYN flood attacks using a SYN cookie. Azure AD B2C also protects against denial-of-service attacks by using limits for rates and connections.
2222

2323
## Password attacks
2424

25-
Azure AD B2C also has mitigation techniques in place for password attacks. Mitigation includes brute-force password attacks and dictionary password attacks. Passwords that are set by users are required to be reasonably complex. By using various signals, Azure AD B2C analyzes the integrity of requests. Azure AD B2C is designed to intelligently differentiate intended users from hackers and botnets. Azure AD B2C provides a sophisticated strategy to lock accounts based on the passwords entered, in the likelihood of an attack.
25+
Passwords that are set by users are required to be reasonably complex. Azure AD B2C has mitigation techniques in place for password attacks. Mitigation includes brute-force password attacks and dictionary password attacks. By using various signals, Azure AD B2C analyzes the integrity of requests. Azure AD B2C is designed to intelligently differentiate intended users from hackers and botnets.
26+
27+
Azure AD B2C uses a sophisticated strategy to lock accounts. The accounts are locked based on the IP of the request and the passwords entered. The duration of the lockout also increases based on the likelihood that it's an attack. After a password is tried 10 times unsuccessfully, a one-minute lockout occurs. The next time a login is unsuccessful after the account is unlocked, another one-minute lockout occurs and continues for each unsuccessful login. Entering the same password repeatedly doesn't count as multiple unsuccessful logins.
28+
29+
The first 10 lockout periods are one minute long. The next 10 lockout periods are slightly longer and increase in duration after every 10 lockout periods. The lockout counter resets to zero after a successful login when the account isn’t locked. Lockout periods can last up to five hours.
30+
31+
Currently, you can't:
32+
33+
- Trigger a lockout with fewer than 10 failed logins
34+
- Retrieve a list of locked out accounts
35+
- Configure the lock out policy
2636

2737
For more information, visit the [Microsoft Trust Center](https://www.microsoft.com/trustcenter/default.aspx).

0 commit comments

Comments
 (0)