Skip to content

Commit 1ea7a8b

Browse files
committed
Bringing even with master.
2 parents e31e113 + 01aeb41 commit 1ea7a8b

File tree

208 files changed

+3378
-3025
lines changed

Some content is hidden

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

208 files changed

+3378
-3025
lines changed

.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -277,6 +277,12 @@
277277
"url": "https://github.com/Azure-Samples/Cognitive-Face-CSharp-sample",
278278
"branch": "master",
279279
"branch_mapping": {}
280+
},
281+
{
282+
"path_to_root": "cognitive-services-face-android-detect",
283+
"url": "https://github.com/Azure-Samples/cognitive-services-face-android-detect",
284+
"branch": "master",
285+
"branch_mapping": {}
280286
}
281287
],
282288
"branch_target_mapping": {

.openpublishing.redirection.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,21 @@
155155
"redirect_url": "/azure/active-directory/users-groups-roles/users-sharing-accounts",
156156
"redirect_document_id": true
157157
},
158+
{
159+
"source_path": "articles/active-directory/fundamentals/active-directory-administer.md",
160+
"redirect_url": "/azure/active-directory/fundamentals/active-directory-whatis",
161+
"redirect_document_id": false
162+
},
163+
{
164+
"source_path": "articles/active-directory/fundamentals/identity-fundamentals.md",
165+
"redirect_url": "/azure/active-directory/fundamentals/active-directory-whatis",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path": "articles/active-directory/fundamentals/understand-azure-identity-solutions.md",
170+
"redirect_url": "/azure/active-directory/fundamentals/active-directory-whatis",
171+
"redirect_document_id": false
172+
},
158173
{
159174
"source_path": "articles/active-directory/fundamentals/active-directory-groups-restore-azure-portal.md",
160175
"redirect_url": "/azure/active-directory/users-groups-roles/groups-restore-deleted",
@@ -3276,6 +3291,11 @@
32763291
"redirect_url": "/azure/application-gateway/tutorial-autoscale-ps",
32773292
"redirect_document_id": false
32783293
},
3294+
{
3295+
"source_path": "articles/application-gateway/application-gateway-create-gateway-portal.md",
3296+
"redirect_url": "/azure/application-gateway/quick-create-portal",
3297+
"redirect_document_id": false
3298+
},
32793299
{
32803300
"source_path": "articles/application-insights/app-insights-azure-diagnostics.md",
32813301
"redirect_url": "/azure/monitoring-and-diagnostics/azure-diagnostics-configure-application-insights",

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ When you use Azure Active Directory (Azure AD) B2C together with Azure Applicati
2727
2828
## How it works
2929

30-
The Identity Experience Framework in Azure AD B2C includes the provider `Handler="Web.TPEngine.Providers.UserJourneyContextProvider, 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.
30+
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.
3131

3232
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.
3333

articles/active-directory/authentication/howto-password-smart-lockout.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.component: authentication
88
ms.topic: conceptual
9-
ms.date: 07/18/2018
9+
ms.date: 11/12/2018
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -18,10 +18,18 @@ ms.reviewer: rogoya
1818

1919
Smart lockout uses cloud intelligence to lock out bad actors who are trying to guess your users’ passwords or use brute-force methods to get in. That intelligence can recognize sign-ins coming from valid users and treat them differently than ones of attackers and other unknown sources. Smart lockout locks out the attackers, while letting your users continue to access their accounts and be productive.
2020

21-
By default, smart lockout locks the account from sign-in attempts for one minute after ten failed attempts. The account locks again after each subsequent failed sign-in attempt, for one minute at first and longer in subsequent attempts.
21+
By default, smart lockout locks the account from sign-in attempts for one minute after 10 failed attempts. The account locks again after each subsequent failed sign-in attempt, for one minute at first and longer in subsequent attempts.
22+
23+
* Smart lockout tracks the last three bad password hashes to avoid reincrementing the lockout counter. If someone enters the same bad password multiple times, this behavior will not cause the account to lockout.
24+
* This functionality is not available for customers with pass-through authentication enabled.
2225

2326
Smart lockout is always on for all Azure AD customers with these default settings that offer the right mix of security and usability. Customization of the smart lockout settings, with values specific to your organization, requires Azure AD Basic or higher licenses for your users.
2427

28+
Using smart lockout does not guarantee that a genuine user will never be locked out. When smart lockout locks a user account, we try our best to not lockout the genuine user. The lockout service attempts to ensure that bad actors can’t gain access to a genuine users account.
29+
30+
* Each Azure Active Directory data center tracks lockout independently. A user will have (threshold_limit * datacenter_count) number of attempts, if the user hits each data center.
31+
* Smart Lockout uses familiar location vs unfamiliar location to differentiate between a bad actor and the genuine user. Unfamiliar and familiar locations will both have separate lockout counters.
32+
2533
Smart lockout can be integrated with hybrid deployments, using password hash sync or pass-through authentication to protect on-premises Active Directory accounts from being locked out by attackers. By setting smart lockout policies in Azure AD appropriately, attacks can be filtered out before they reach on-premises Active Directory.
2634

2735
When using [pass-through authentication](../hybrid/how-to-connect-pta.md), you need to make sure that:

articles/active-directory/conditional-access/technical-reference.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,13 +123,13 @@ This setting works with all browsers. However, to satisfy a device policy, like
123123

124124
| OS | Browsers | Support |
125125
| :-- | :-- | :-: |
126-
| Windows 10 | Internet Explorer, Edge, Chrome | ![Check][1] |
126+
| Windows 10 | Internet Explorer, Microsoft Edge, Chrome | ![Check][1] |
127127
| Windows 8 / 8.1 | Internet Explorer, Chrome | ![Check][1] |
128128
| Windows 7 | Internet Explorer, Chrome | ![Check][1] |
129129
| iOS | Safari, Intune Managed Browser | ![Check][1] |
130130
| Android | Chrome, Intune Managed Browser | ![Check][1] |
131-
| Windows Phone | Internet Explorer, Edge | ![Check][1] |
132-
| Windows Server 2016 | Internet Explorer, Edge | ![Check][1] |
131+
| Windows Phone | Internet Explorer, Microsoft Edge | ![Check][1] |
132+
| Windows Server 2016 | Internet Explorer, Microsoft Edge | ![Check][1] |
133133
| Windows Server 2016 | Chrome | Coming soon |
134134
| Windows Server 2012 R2 | Internet Explorer, Chrome | ![Check][1] |
135135
| Windows Server 2008 R2 | Internet Explorer, Chrome | ![Check][1] |

articles/active-directory/develop/howto-v1-debug-saml-sso-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ We recommend installing the [My Apps Secure Sign-in Extension](../user-help/acti
2828
To download and install the My Apps Secure Sign-in Extension, use one of the following links.
2929

3030
- [Chrome](https://go.microsoft.com/fwlink/?linkid=866367)
31-
- [Edge](https://go.microsoft.com/fwlink/?linkid=845176)
31+
- [Microsoft Edge](https://go.microsoft.com/fwlink/?linkid=845176)
3232
- [Firefox](https://go.microsoft.com/fwlink/?linkid=866366)
3333

3434

articles/active-directory/fundamentals/active-directory-administer.md

Lines changed: 0 additions & 117 deletions
This file was deleted.

0 commit comments

Comments
 (0)