Skip to content

Commit fb290f3

Browse files
committed
Merge branch 'master' of https://github.com/Microsoft/azure-docs-pr into tmoverviewmvc
2 parents 42dca05 + 5fa673b commit fb290f3

File tree

11 files changed

+172
-97
lines changed

11 files changed

+172
-97
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26539,6 +26539,11 @@
2653926539
"source_path": "articles/security/azure-security-disk-encryption.md",
2654026540
"redirect_url": "/azure/security/azure-security-disk-encryption-overview",
2654126541
"redirect_document_id": true
26542+
},
26543+
{
26544+
"source_path": "articles/active-directory/device-management-hybrid-azuread-joined-devices-setup.md",
26545+
"redirect_url": "/azure/active-directory/devices/hybrid-azuread-join-manual-steps",
26546+
"redirect_document_id": true
2654226547
}
2654326548
]
2654426549
}

articles/active-directory/TOC.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@
167167

168168
#### [Set up Azure AD registered Windows 10 devices](user-help/device-management-azuread-registered-devices-windows10-setup.md)
169169
#### [Set up Azure AD joined devices](user-help/device-management-azuread-joined-devices-setup.md)
170-
#### [Set up hybrid Azure AD joined devices](device-management-hybrid-azuread-joined-devices-setup.md)
170+
#### [Set up hybrid Azure AD joined devices](devices/hybrid-azuread-join-manual-steps.md)
171171
#### [Deploy on-premises](active-directory-device-registration-on-premises-setup.md)
172172
#### [Azure AD join during Windows 10 first-run experience](device-management-azuread-joined-devices-frx.md)
173173
### Troubleshoot

articles/active-directory/active-directory-device-registration-on-premises-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ There are many different ways to communicate this URL to your users. For example
160160
### Join a Windows 7 device by using Azure Active Directory device registration
161161
To register Windows 7 domain-joined devices, you need to deploy the [device registration software package](https://www.microsoft.com/download/details.aspx?id=53554).
162162

163-
For instructions about how to use the package, see [Windows Installer packages for non-Windows 10 computers](device-management-hybrid-azuread-joined-devices-setup.md#windows-installer-packages-for-non-windows-10-computers).
163+
For instructions about how to use the package, see [Windows Installer packages for non-Windows 10 computers](devices/hybrid-azuread-join-manual-steps.md#windows-installer-packages-for-non-windows-10-computers).
164164

165165
## Verify that registered devices are written back to Active Directory
166166
You can view and verify that your device objects have been written back to your Active Directory by using LDP.exe or ADSI Edit. Both are available with the Active Directory administrator tools.

articles/active-directory/device-management-hybrid-azuread-joined-devices-setup.md renamed to articles/active-directory/devices/hybrid-azuread-join-manual-steps.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: How to configure hybrid Azure Active Directory joined devices | Microsoft Docs
3-
description: Learn how to configure hybrid Azure Active Directory joined devices.
2+
title: Configure hybrid Azure Active Directory joined devices manually | Microsoft Docs
3+
description: Learn how to manually configure hybrid Azure Active Directory joined devices.
44
services: active-directory
55
documentationcenter: ''
66
author: MarkusVi
@@ -14,18 +14,23 @@ ms.workload: identity
1414
ms.tgt_pltfrm: na
1515
ms.devlang: na
1616
ms.topic: article
17-
ms.date: 03/15/2018
17+
ms.date: 07/31/2018
1818
ms.author: markvi
19-
ms.reviewer: jairoc
19+
ms.reviewer: sandeo
2020

2121
---
22-
# How to configure hybrid Azure Active Directory joined devices
22+
# Tutorial: Configure hybrid Azure Active Directory joined devices manually
2323

24-
With device management in Azure Active Directory (Azure AD), you can ensure that your users are accessing your resources from devices that meet your standards for security and compliance. For more details, see [Introduction to device management in Azure Active Directory](device-management-introduction.md).
24+
With device management in Azure Active Directory (Azure AD), you can ensure that your users are accessing your resources from devices that meet your standards for security and compliance. For more details, see [../Introduction to device management in Azure Active Directory](../device-management-introduction.md).
2525

2626
If you have an on-premises Active Directory environment and you want to join your domain-joined devices to Azure AD, you can accomplish this by configuring hybrid Azure AD joined devices. This article provides you with the related steps.
2727

2828

29+
30+
> [!TIP]
31+
> If using Azure AD Connect is an option for you, see [Select your scenario](hybrid-azuread-join-plan.md#select-your-scenario). By using Azure AD Connect, you can simplify the configuration of hybrid Azure AD join significantly.
32+
33+
2934
## Before you begin
3035

3136
Before you start configuring hybrid Azure AD joined devices in your environment, you should familiarize yourself with the supported scenarios and the constraints.
@@ -187,10 +192,10 @@ In the script above,
187192

188193
- `$verifiedDomain = "contoso.com"` is a placeholder you need to replace with one of your verified domain names in Azure AD. You will have to own the domain before you can use it.
189194

190-
For more details about verified domain names, see [Add a custom domain name to Azure Active Directory](active-directory-domains-add-azure-portal.md).
195+
For more details about verified domain names, see [Add a custom domain name to Azure Active Directory](../active-directory-domains-add-azure-portal.md).
191196
To get a list of your verified company domains, you can use the [Get-AzureADDomain](/powershell/module/Azuread/Get-AzureADDomain?view=azureadps-2.0) cmdlet.
192197

193-
![Get-AzureADDomain](./media/active-directory-conditional-access-automatic-device-registration-setup/01.png)
198+
![Get-AzureADDomain](./media/hybrid-azuread-join-manual-steps/01.png)
194199

195200
## Step 2: Setup issuance of claims
196201

@@ -333,11 +338,11 @@ In the claim above,
333338

334339

335340

336-
For more details about verified domain names, see [Add a custom domain name to Azure Active Directory](active-directory-domains-add-azure-portal.md).
341+
For more details about verified domain names, see [Add a custom domain name to Azure Active Directory](../active-directory-domains-add-azure-portal.md).
337342

338343
To get a list of your verified company domains, you can use the [Get-MsolDomain](/powershell/module/msonline/get-msoldomain?view=azureadps-1.0) cmdlet.
339344

340-
![Get-MsolDomain](./media/active-directory-conditional-access-automatic-device-registration-setup/01.png)
345+
![Get-MsolDomain](./media/hybrid-azuread-join-manual-steps/01.png)
341346

342347
### Issue ImmutableID for computer when one for users exist (e.g. alternate login ID is set)
343348

@@ -514,7 +519,7 @@ To register Windows down-level devices, you need to make sure that the setting t
514519

515520
The following policy must be set to **All**: **Users may register their devices with Azure AD**
516521

517-
![Register devices](./media/active-directory-conditional-access-automatic-device-registration-setup/23.png)
522+
![Register devices](./media/hybrid-azuread-join-manual-steps/23.png)
518523

519524

520525
### Configure on-premises federation service
@@ -611,9 +616,9 @@ The output of this cmdlet shows devices that are registered and joined with Azur
611616

612617
## Next steps
613618

614-
* [Introduction to device management in Azure Active Directory](device-management-introduction.md)
619+
* [Introduction to device management in Azure Active Directory](../device-management-introduction.md)
615620

616621

617622

618623
<!--Image references-->
619-
[1]: ./media/active-directory-conditional-access-automatic-device-registration-setup/12.png
624+
[1]: ./media/hybrid-azuread-join-manual-steps/12.png
6.14 KB
Loading
412 Bytes
Loading
3.06 KB
Loading

articles/azure-functions/functions-reference-node.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ The following table shows the Node.js version used by each major version of the
267267
| Functions version | Node.js version |
268268
|---|---|
269269
| 1.x | 6.11.2 (locked by the runtime) |
270-
| 2.x |>=8.4.0 with current LTS 8.9.4 recommended. Set the version by using the WEBSITE_NODE_DEFAULT_VERSION [app setting](functions-how-to-use-azure-function-app-settings.md#settings).|
270+
| 2.x | _Active LTS_ and _Current_ Node.js versions (8.11.1 and 10.6.0 recommended). Set the version by using the WEBSITE_NODE_DEFAULT_VERSION [app setting](functions-how-to-use-azure-function-app-settings.md#settings).|
271271

272272
You can see the current version that the runtime is using by printing `process.version` from any function.
273273

articles/key-vault/TOC.md

Lines changed: 0 additions & 80 deletions
This file was deleted.
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
### YamlMime:ContextObject
22
brand: azure
33
breadcrumb_path: ../breadcrumb/toc.yml
4-
toc_rel: ../TOC.md
4+
toc_rel: ../toc.yml

0 commit comments

Comments
 (0)