Skip to content

Commit e2e342d

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into labspecific0521
2 parents 7eb5eb7 + af0ba7b commit e2e342d

File tree

123 files changed

+404
-2272
lines changed

Some content is hidden

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

123 files changed

+404
-2272
lines changed

.openpublishing.redirection.json

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8710,6 +8710,56 @@
87108710
"redirect_url": "/azure/cognitive-services/video-indexer/video-indexer-get-started",
87118711
"redirect_document_id": false
87128712
},
8713+
{
8714+
"source_path": "articles/iot-suite/iot-suite-v1-connecting-devices.md",
8715+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-connecting-devices.md",
8716+
"redirect_document_id": false
8717+
},
8718+
{
8719+
"source_path": "articles/iot-suite/iot-suite-v1-connecting-devices-linux.md",
8720+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-connecting-devices-linux.md",
8721+
"redirect_document_id": false
8722+
},
8723+
{
8724+
"source_path": "articles/iot-suite/iot-suite-v1-connecting-devices-node.md",
8725+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-connecting-devices-node.md",
8726+
"redirect_document_id": false
8727+
},
8728+
{
8729+
"source_path": "articles/iot-suite/iot-suite-v1-custom-rule.md",
8730+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-custom-rule.md",
8731+
"redirect_document_id": false
8732+
},
8733+
{
8734+
"source_path": "articles/iot-suite/iot-suite-v1-dynamic-telemetry.md",
8735+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-dynamic-telemetry.md",
8736+
"redirect_document_id": false
8737+
},
8738+
{
8739+
"source_path": "articles/iot-suite/iot-suite-v1-faq.md",
8740+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-faq.md",
8741+
"redirect_document_id": false
8742+
},
8743+
{
8744+
"source_path": "articles/iot-suite/iot-suite-v1-getstarted-preconfigured-solutions.md",
8745+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-getstarted-preconfigured-solutions.md",
8746+
"redirect_document_id": false
8747+
},
8748+
{
8749+
"source_path": "articles/iot-suite/iot-suite-v1-guidance-on-customizing-preconfigured-solutions.md",
8750+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-guidance-on-customizing-preconfigured-solutions.md",
8751+
"redirect_document_id": false
8752+
},
8753+
{
8754+
"source_path": "articles/iot-suite/iot-suite-v1-logic-apps-tutorial.md",
8755+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-logic-apps-tutorial.md",
8756+
"redirect_document_id": false
8757+
},
8758+
{
8759+
"source_path": "articles/iot-suite/iot-suite-v1-permissions.md",
8760+
"redirect_url": "https://github.com/Azure/azure-iot-remote-monitoring/blob/master/Tutorials/iot-suite-v1-permissions.md",
8761+
"redirect_document_id": false
8762+
},
87138763
{
87148764
"source_path": "articles/iot-suite/iot-solution-build-system.md",
87158765
"redirect_url": "https://github.com/Azure-Samples/MyDriving/blob/master/docs/iot-solution-build-system.md",

articles/active-directory-domain-services/active-directory-ds-faqs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: identity
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: article
16-
ms.date: 03/08/2018
16+
ms.date: 05/23/2018
1717
ms.author: maheshu
1818

1919
---
@@ -79,6 +79,9 @@ Yes. Members of the 'AAD DC Administrators' group are granted 'DNS Administrator
7979
### What is the password lifetime policy on a managed domain?
8080
The default password lifetime on an Azure AD Domain Services managed domain is 90 days. This password lifetime is not synchronized with the password lifetime configured in Azure AD. Therefore, you may have a situation where users' passwords expire in your managed domain, but are still valid in Azure AD. In such scenarios, users need to change their password in Azure AD and the new password will synchronize to your managed domain. Additionally, the 'password-does-not-expire' and 'user-must-change-password-at-next-logon' attributes for user accounts are not synchronized to your managed domain.
8181

82+
### Does Azure AD Domain Services provide AD account lockout protection?
83+
Yes. 4 invalid password attempts within 2 minutes on the managed domain cause a user account to be locked out for 30 minutes. After 30 minutes, the user account is automatically unlocked. Invalid password attempts on the managed domain do not lock out the user account in Azure AD. The user account is locked out only within your Azure AD Domain Services managed domain.
84+
8285
## Billing and availability
8386
### Is Azure AD Domain Services a paid service?
8487
Yes. For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/active-directory-ds/).

articles/active-directory-domain-services/active-directory-ds-features.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: identity
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: article
16-
ms.date: 03/06/2017
16+
ms.date: 05/23/2018
1717
ms.author: maheshu
1818

1919
---
@@ -35,4 +35,5 @@ The following features are available in Azure AD Domain Services managed domains
3535
* **Create custom Organizational Units (OUs):** Members of the 'AAD DC Administrators' group can create custom OUs in the managed domain. These users are granted full administrative privileges over custom OUs, so they can add/remove service accounts, computers, groups etc. within these custom OUs.
3636
* **Available in multiple Azure regions:** See the [Azure services by region](https://azure.microsoft.com/regions/#services/) page to know the Azure regions in which Azure AD Domain Services is available.
3737
* **High availability:** Azure AD Domain Services offers high availability for your domain. This feature offers the guarantee of higher service uptime and resilience to failures. Built-in health monitoring offers automated remediation from failures by spinning up new instances to replace failed instances and to provide continued service for your domain.
38+
* **AD Account lockout protection:** Users accounts are locked out for 30 minutes if 4 invalid password attempts are encountered within 2 minutes. Accounts are automatically unlocked after 30 minutes.
3839
* **Use familiar management tools:** You can use familiar Windows Server Active Directory management tools such as the Active Directory Administrative Center or Active Directory PowerShell to administer managed domains.

articles/active-directory/groups-naming-policy.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -187,8 +187,7 @@ School Data Sync (SDS) | Groups created through SDS comply with naming policy, b
187187
Outlook Customer Manager (OCM) | Outlook Customer Manager is compliant with the naming policy, which is automatically applied to the group created in Outlook Customer Manager. If a custom blocked word is detected, group creation in OCM is blocked, and the user is blocked from using the OCM app.
188188
Classroom app | Groups created in Classroom app comply with the naming policy, but the naming policy isn't applied automatically, and the naming policy preview isn't shown to the users while entering a classroom group name. Users must enter the enforced classroom group name with prefixes and suffixes. If not, the classroom group create or edit operation fails with errors.
189189
Power BI | Power BI workspaces are compliant with the naming policy.
190-
Yammer | When a user signed in to Yammer with their Azure Active Directory account creates a group or edits a group name, the group name will comply with naming policy. This applies both to Office 365 connected groups and all other Yammer groups.
191-
If an Office 365 connected group was created before the naming policy is in place, the group name will not automatically follow the naming policies. When a user edits the group name, they will be prompted to add the prefix and suffix.
190+
Yammer | When a user signed in to Yammer with their Azure Active Directory account creates a group or edits a group name, the group name will comply with naming policy. This applies both to Office 365 connected groups and all other Yammer groups.<br>If an Office 365 connected group was created before the naming policy is in place, the group name will not automatically follow the naming policies. When a user edits the group name, they will be prompted to add the prefix and suffix.
192191
StaffHub | StaffHub teams do not follow the naming policy, but the underlying Office 365 group does. StaffHub team name does not apply the prefixes and suffixes and does not check for custom blocked words. But StaffHub does apply the prefixes and suffixes and removes blocked words from the underlying Office 365 group.
193192
Exchange PowerShell | Exchange PowerShell cmdlets are compliant with the naming policy. Users receive appropriate error messages with suggested prefixes and suffixes and for custom blocked words if they don't follow the naming policy in the group name and group alias (mailNickname).
194193
Azure Active Directory PowerShell cmdlets | Azure Active Directory PowerShell cmdlets are compliant with naming policy. Users receive appropriate error messages with suggested prefixes and suffixes and for custom blocked words if they don't follow the naming convention in group names and group alias.

articles/azure-maps/about-azure-maps.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,13 @@
11
---
22
title: Overview of Azure Maps | Microsoft Docs
33
description: An introduction to Azure Maps
4-
services: azure-maps
5-
keywords:
64
author: kgremban
75
ms.author: kgremban
86
ms.date: 05/07/2018
97
ms.topic: overview
108
ms.service: azure-maps
11-
12-
documentationcenter: ''
9+
services: azure-maps
1310
manager: timlt
14-
ms.devlang: na
1511
ms.custom: mvc
1612
---
1713

articles/azure-maps/consumption-model.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,13 @@
11
---
22
title: Consumption Model in Azure Maps | Microsoft Docs
33
description: Learn about consumption model in Azure Maps
4-
services: azure-maps
5-
keywords:
64
author: subbarayudukamma
75
ms.author: skamma
8-
ms.date: 5/8/2018
9-
ms.topic: article
6+
ms.date: 05/08/2018
7+
ms.topic: conceptual
108
ms.service: azure-maps
11-
12-
documentationcenter: ''
13-
manager: timlt
14-
ms.devlang: na
15-
ms.custom:
9+
services: azure-maps
10+
manager:
1611
---
1712

1813

articles/azure-maps/extend-geojson.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,13 @@
11
---
22
title: Extending GeoJSON geometries in Azure Maps | Microsoft Docs
33
description: Learn how to extend GeoJSON geometries in Azure Maps
4-
services: azure-maps
5-
keywords:
64
author: sataneja
75
ms.author: sataneja
8-
ms.date: 5/17/2018
9-
ms.topic: article
6+
ms.date: 05/17/2018
7+
ms.topic: conceptual
108
ms.service: azure-maps
11-
12-
documentationcenter: ''
13-
manager: timlt
14-
ms.devlang: na
15-
ms.custom:
9+
services: azure-maps
10+
manager:
1611
---
1712

1813

articles/azure-maps/geocoding-coverage.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,13 @@
11
---
22
title: Geocoding Coverage in Azure Maps | Microsoft Docs
33
description: Learn about Geocoding Coverage in Azure Maps
4-
services: azure-maps
5-
keywords:
64
author: kgremban
75
ms.author: kgremban
86
ms.date: 05/07/2018
9-
ms.topic: article
7+
ms.topic: conceptual
108
ms.service: azure-maps
11-
12-
documentationcenter: ''
9+
services: azure-maps
1310
manager: timlt
14-
ms.devlang: na
15-
ms.custom: mvc
1611
---
1712

1813
# Azure Maps geocoding coverage

articles/azure-maps/how-to-manage-account-keys.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: How to manage your Azure Maps account and keys | Microsoft Docs
33
description: You can use the Azure portal to manage your Azure Maps account and manage your access keys.
4-
services: azure-maps
54
author: kgremban
65
ms.author: kgremban
76
ms.date: 05/07/2018
8-
ms.topic: article
7+
ms.topic: conceptual
98
ms.service: azure-maps
9+
services: azure-maps
1010
manager: timlt
1111
---
1212

articles/azure-maps/how-to-search-for-address.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,13 @@
22
# Mandatory fields. See more on aka.ms/skyeye/meta.
33
title: How to search for an address using the Azure Maps Search service | Microsoft Docs
44
description: Learn how to search for an address using the Azure Maps Search service
5-
services: azure-maps
65
author: kgremban
76
ms.author: kgremban
87
ms.date: 05/07/2018
9-
ms.topic: article
8+
ms.topic: conceptual
109
ms.service: azure-maps
10+
services: azure-maps
11+
manager: timlt
1112
---
1213
# How to find an address using the Azure Maps search service
1314

0 commit comments

Comments
 (0)