Skip to content

Commit 46f4b2d

Browse files
authored
Merge pull request #184201 from billmath/holiday1
updating
2 parents eca6235 + 65409e6 commit 46f4b2d

9 files changed

+16
-16
lines changed

articles/active-directory/hybrid/choose-ad-authn.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@ title: Authentication for Azure AD hybrid identity solutions
33
titleSuffix: Active Directory
44
description: This guide helps CEOs, CIOs, CISOs, Chief Identity Architects, Enterprise Architects, and Security and IT decision makers responsible for choosing an authentication method for their Azure AD hybrid identity solution in medium to large organizations.
55
keywords:
6-
author: martincoetzer
7-
ms.author: martinco
8-
ms.date: 10/30/2019
6+
author: billmath
7+
ms.author: billmath
8+
ms.date: 01/05/2022
99
ms.topic: article
1010
ms.service: security
1111
ms.subservice: security-fundamentals
@@ -215,4 +215,4 @@ In today’s world, threats are present 24 hours a day and come from everywhere.
215215

216216
[Get started](../fundamentals/active-directory-whatis.md) with Azure AD and deploy the right authentication solution for your organization.
217217

218-
If you're thinking about migrating from federated to cloud authentication, learn more about [changing the sign-in method](../../active-directory/hybrid/plan-connect-user-signin.md). To help you plan and implement the migration, use [these project deployment plans](../fundamentals/active-directory-deployment-plans.md) or consider using the new [Staged Rollout](../../active-directory/hybrid/how-to-connect-staged-rollout.md) feature to migrate federated users to using cloud authentication in a staged approach.
218+
If you're thinking about migrating from federated to cloud authentication, learn more about [changing the sign-in method](../../active-directory/hybrid/plan-connect-user-signin.md). To help you plan and implement the migration, use [these project deployment plans](../fundamentals/active-directory-deployment-plans.md) or consider using the new [Staged Rollout](../../active-directory/hybrid/how-to-connect-staged-rollout.md) feature to migrate federated users to using cloud authentication in a staged approach.

articles/active-directory/hybrid/cloud-governed-management-for-on-premises.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.workload: identity
99
ms.tgt_pltfrm: na
1010
ms.topic: conceptual
11-
ms.date: 05/29/2020
11+
ms.date: 01/05/2022
1212
ms.subservice: hybrid
1313
ms.author: billmath
1414
ms.collection: M365-identity-device-management
@@ -112,4 +112,4 @@ In hybrid environments, Microsoft's strategy is to enable deployments where the
112112

113113
## Next steps
114114

115-
For more information on how to get started on this journey, see the Azure AD deployment plans, located at <https://aka.ms/deploymentplans>. They provide end-to-end guidance about how to deploy Azure Active Directory (Azure AD) capabilities. Each plan explains the business value, planning considerations, design, and operational procedures needed to successfully roll out common Azure AD capabilities. Microsoft continually updates the deployment plans with best practices learned from customer deployments and other feedback when we add new capabilities to managing from the cloud with Azure AD.
115+
For more information on how to get started on this journey, see the Azure AD deployment plans, located at <https://aka.ms/deploymentplans>. They provide end-to-end guidance about how to deploy Azure Active Directory (Azure AD) capabilities. Each plan explains the business value, planning considerations, design, and operational procedures needed to successfully roll out common Azure AD capabilities. Microsoft continually updates the deployment plans with best practices learned from customer deployments and other feedback when we add new capabilities to managing from the cloud with Azure AD.

articles/active-directory/hybrid/how-to-connect-device-writeback.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: active-directory
1212
ms.workload: identity
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 05/08/2018
15+
ms.date: 01/05/2022
1616
ms.subservice: hybrid
1717
ms.author: billmath
1818

@@ -125,4 +125,4 @@ Verify configuration in Active Directory:
125125
* [Setting up On-premises Conditional Access using Azure Active Directory Device Registration](../devices/overview.md)
126126

127127
## Next steps
128-
Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).
128+
Learn more about [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).

articles/active-directory/hybrid/how-to-connect-emergency-ad-fs-certificate-rotation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ manager: karenhoran
66
ms.service: active-directory
77
ms.workload: identity
88
ms.topic: how-to
9-
ms.date: 03/22/2021
9+
ms.date: 01/05/2022
1010
ms.subservice: hybrid
1111
ms.author: billmath
1212
---

articles/active-directory/hybrid/how-to-connect-fed-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: active-directory
1111
ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.topic: how-to
14-
ms.date: 08/23/2018
14+
ms.date: 01/05/2022
1515
ms.subservice: hybrid
1616
ms.author: billmath
1717

articles/active-directory/hybrid/how-to-connect-fed-group-claims.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.subservice: hybrid
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 12/13/2021
12+
ms.date: 01/05/2022
1313
ms.author: billmath
1414
author: billmath
1515
---

articles/active-directory/hybrid/how-to-connect-fed-hybrid-azure-ad-join-post-config-tasks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: active-directory
1111
ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.topic: how-to
14-
ms.date: 08/10/2018
14+
ms.date: 01/05/2022
1515
ms.subservice: hybrid
1616
ms.author: billmath
1717

articles/active-directory/hybrid/how-to-connect-fed-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.service: active-directory
1313
ms.workload: identity
1414
ms.tgt_pltfrm: na
1515
ms.topic: how-to
16-
ms.date: 07/18/2017
16+
ms.date: 01/05/2022
1717
ms.subservice: hybrid
1818
ms.author: billmath
1919
ms.custom: seohack1
@@ -257,4 +257,4 @@ In this rule, you're simply checking the temporary flag **idflag**. You decide w
257257
You can add more than one domain to be federated by using Azure AD Connect, as described in [Add a new federated domain](how-to-connect-fed-management.md#addfeddomain). Azure AD Connect version 1.1.553.0 and latest creates the correct claim rule for issuerID automatically. If you cannot use Azure AD Connect version 1.1.553.0 or latest, it is recommended that [Azure AD RPT Claim Rules](https://aka.ms/aadrptclaimrules) tool is used to generate and set correct claim rules for the Azure AD relying party trust.
258258

259259
## Next steps
260-
Learn more about [user sign-in options](plan-connect-user-signin.md).
260+
Learn more about [user sign-in options](plan-connect-user-signin.md).

articles/active-directory/hybrid/how-to-connect-fed-o365-certs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: active-directory
1111
ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.topic: how-to
14-
ms.date: 10/20/2017
14+
ms.date: 01/05/2022
1515
ms.subservice: hybrid
1616
ms.author: billmath
1717

@@ -189,4 +189,4 @@ By default, AD FS is configured to generate token signing and token decryption c
189189

190190
Azure AD tries to retrieve a new certificate from your federation service metadata 30 days before the expiry of the current certificate. In case a new certificate is not available at that time, Azure AD will continue to monitor the metadata on regular daily intervals. As soon as the new certificate is available in the metadata, the federation settings for the domain are updated with the new certificate information. You can use `Get-MsolDomainFederationSettings` to verify if you see the new certificate in the NextSigningCertificate / SigningCertificate.
191191

192-
For more information on Token Signing certificates in AD FS see [Obtain and Configure Token Signing and Token Decryption Certificates for AD FS](/windows-server/identity/ad-fs/operations/configure-ts-td-certs-ad-fs)
192+
For more information on Token Signing certificates in AD FS see [Obtain and Configure Token Signing and Token Decryption Certificates for AD FS](/windows-server/identity/ad-fs/operations/configure-ts-td-certs-ad-fs)

0 commit comments

Comments
 (0)