Skip to content

Commit 684b6f8

Browse files
author
Kimmo Forss
committed
2 parents c68fea5 + 70f3352 commit 684b6f8

File tree

802 files changed

+6894
-6057
lines changed

Some content is hidden

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

802 files changed

+6894
-6057
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -755,7 +755,7 @@
755755
{
756756
"path_to_root": "azure-spring-apps-reference-architecture",
757757
"url": "https://github.com/Azure/azure-spring-apps-reference-architecture",
758-
"branch": "main",
758+
"branch": "reference-architecture",
759759
"branch_mapping": {}
760760
},
761761
{

articles/active-directory-b2c/configure-authentication-sample-ios-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: CelesteDG
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: reference
10-
ms.date: 07/29/2021
10+
ms.date: 01/06/2023
1111
ms.author: kengaderdus
1212
ms.subservice: B2C
1313
ms.custom: "b2c-support"
@@ -110,10 +110,10 @@ This sample acquires an access token with the relevant scopes that the mobile ap
110110
111111
## Step 4: Get the iOS mobile app sample
112112

113-
1. [Download the .zip file](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal/archive/refs/heads/vNext.zip), or clone the sample web app from the [GitHub repo](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal).
113+
1. [Download the .zip file](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal/archive/refs/heads/master.zip), or clone the sample web app from the [GitHub repo](https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal).
114114

115115
```bash
116-
git clone https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal/tree/vNext.git
116+
git clone https://github.com/Azure-Samples/active-directory-b2c-ios-swift-native-msal
117117
```
118118

119119
1. Use [CocoaPods](https://cocoapods.org/) to install the MSAL library. In a terminal window, go to the project root folder. This folder contains the *podfile* file. Run the following command:

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,30 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Azure Active Directory](../active-directory/fundamentals/whats-new.md) and [Azure AD B2C developer release notes](custom-policy-developer-notes.md)
1717

18+
## December 2022
19+
20+
### New articles
21+
22+
- [Build a global identity solution with funnel-based approach](azure-ad-b2c-global-identity-funnel-based-design.md)
23+
- [Azure Active Directory B2C global identity framework proof of concept for funnel-based configuration](azure-ad-b2c-global-identity-proof-of-concept-funnel.md)
24+
- [Azure Active Directory B2C global identity framework proof of concept for region-based configuration](azure-ad-b2c-global-identity-proof-of-concept-regional.md)
25+
- [Build a global identity solution with region-based approach](azure-ad-b2c-global-identity-region-based-design.md)
26+
- [Azure Active Directory B2C global identity framework](azure-ad-b2c-global-identity-solutions.md)
27+
28+
### Updated articles
29+
30+
- [Set up a resource owner password credentials flow in Azure Active Directory B2C](add-ropc-policy.md)
31+
- [Use API connectors to customize and extend sign-up user flows and custom policies with external identity data sources](api-connectors-overview.md)
32+
- [Azure Active Directory B2C: Region availability & data residency](data-residency.md)
33+
- [Tutorial: Configure Experian with Azure Active Directory B2C](partner-experian.md)
34+
- [Tutorial: Configure Microsoft Dynamics 365 Fraud Protection with Azure Active Directory B2C](partner-dynamics-365-fraud-protection.md)
35+
- [Tutorial: Configure Azure Active Directory B2C with Datawiza to provide secure hybrid access](partner-datawiza.md)
36+
- [Configure TheAccessHub Admin Tool with Azure Active Directory B2C](partner-n8identity.md)
37+
- [Tutorial: Configure Cloudflare Web Application Firewall with Azure Active Directory B2C](partner-cloudflare.md)
38+
- [Set up a password reset flow in Azure Active Directory B2C](add-password-reset-policy.md)
39+
- [What is Azure Active Directory B2C?](overview.md)
40+
- [Technical and feature overview of Azure Active Directory B2C](technical-overview.md)
41+
1842
## November 2022
1943

2044
### New articles
@@ -138,4 +162,4 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
138162
- [Application types that can be used in Active Directory B2C](application-types.md)
139163
- [Publish your Azure Active Directory B2C app to the Azure Active Directory app gallery](publish-app-to-azure-ad-app-gallery.md)
140164
- [Quickstart: Set up sign in for a desktop app using Azure Active Directory B2C](quickstart-native-app-desktop.md)
141-
- [Register a single-page application (SPA) in Azure Active Directory B2C](tutorial-register-spa.md)
165+
- [Register a single-page application (SPA) in Azure Active Directory B2C](tutorial-register-spa.md)

articles/active-directory/authentication/howto-mfa-nps-extension.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -104,11 +104,11 @@ When you install the extension, you need the *Tenant ID* and admin credentials f
104104

105105
### Network requirements
106106

107-
The NPS server must be able to communicate with the following URLs over ports 80 and 443:
107+
The NPS server must be able to communicate with the following URLs over TCP port 443:
108108

109-
* *https:\//strongauthenticationservice.auth.microsoft.com*
110-
* *https:\//strongauthenticationservice.auth.microsoft.us*
111-
* *https:\//strongauthenticationservice.auth.microsoft.cn*
109+
* *https:\//strongauthenticationservice.auth.microsoft.com* (for Azure Public cloud customers).
110+
* *https:\//strongauthenticationservice.auth.microsoft.us* (for Azure Government customers).
111+
* *https:\//strongauthenticationservice.auth.microsoft.cn* (for Azure China 21Vianet customers).
112112
* *https:\//adnotifications.windowsazure.com*
113113
* *https:\//login.microsoftonline.com*
114114
* *https:\//credentials.azure.com*

articles/active-directory/conditional-access/howto-continuous-access-evaluation-troubleshoot.md

Lines changed: 2 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.subservice: conditional-access
88
ms.topic: troubleshooting
9-
ms.date: 06/09/2022
9+
ms.date: 01/05/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -35,7 +35,7 @@ There are multiple sign-in requests for each authentication. Some will be shown
3535

3636
### Searching for specific sign-in attempts
3737

38-
Use filters to narrow your search. For example, if a user signed in to Teams, use the Application filter and set it to Teams. Admins may need to check the sign-ins from both interactive and non-interactive tabs to locate the specific sign-in. To further narrow the search, admins may apply multiple filters.
38+
Sign in logs contain information on Success as well as failure events. Use filters to narrow your search. For example, if a user signed in to Teams, use the Application filter and set it to Teams. Admins may need to check the sign-ins from both interactive and non-interactive tabs to locate the specific sign-in. To further narrow the search, admins may apply multiple filters.
3939

4040
## Continuous access evaluation workbooks
4141

articles/active-directory/develop/authentication-vs-authorization.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,17 @@
22
title: Authentication vs. authorization
33
description: Learn about the basics of authentication and authorization in the Microsoft identity platform.
44
services: active-directory
5-
author: rwike77
5+
author: cilwerner
66
manager: CelesteDG
77

88
ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: conceptual
1111
ms.workload: identity
1212
ms.date: 11/02/2022
13-
ms.author: ryanwi
13+
ms.author: cwerner
1414
ms.reviewer: jmprieur, saeeda, sureshja, ludwignick
15-
ms.custom: aaddev, identityplatformtop40, scenarios:getting-started
15+
ms.custom: aaddev, identityplatformtop40, microsoft-identity-platform, scenarios:getting-started
1616
#Customer intent: As an application developer, I want to understand the basic concepts of authentication and authorization in the Microsoft identity platform.
1717
---
1818

articles/active-directory/devices/howto-vm-sign-in-azure-ad-windows.md

Lines changed: 2 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.subservice: devices
88
ms.topic: how-to
9-
ms.date: 06/16/2022
9+
ms.date: 01/05/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -416,7 +416,7 @@ Set-MsolUser -UserPrincipalName [email protected] -StrongAuthenticationRequir
416416
If you haven't deployed Windows Hello for Business and if that isn't an option for now, you can configure a Conditional Access policy that excludes the Azure Windows VM Sign-In app from the list of cloud apps that require MFA. To learn more about Windows Hello for Business, see [Windows Hello for Business overview](/windows/security/identity-protection/hello-for-business/hello-identity-verification).
417417

418418
> [!NOTE]
419-
> Windows Hello for Business PIN authentication with RDP has been supported for several versions of Windows 10. Support for biometric authentication with RDP was added in Windows 10 version 1809. Using Windows Hello for Business authentication during RDP is available only for deployments that use a certificate trust model. It's currently not available for a key trust model.
419+
> Windows Hello for Business PIN authentication with RDP has been supported for several versions of Windows 10. Support for biometric authentication with RDP was added in Windows 10 version 1809. Using Windows Hello for Business authentication during RDP is available for deployments that use a certificate trust model or key trust model.
420420
421421
Share your feedback about this feature or report problems with using it on the [Azure AD feedback forum](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789).
422422

articles/active-directory/enterprise-users/groups-dynamic-rule-member-of.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ Only administrators in the Global Administrator, Intune Administrator, or User A
3737
- MemberOf can't be used with other rules. For example, a rule that states dynamic group A should contain members of group B and also should contain only users located in Redmond will fail.
3838
- Dynamic group rule builder and validate feature can't be used for memberOf at this time.
3939
- MemberOf can't be used with other operators. For example, you can't create a rule that states “Members Of group A can't be in Dynamic group B.”
40-
- The objects specified in the rule can't be administrative units.
4140

4241
## Getting started
4342

articles/active-directory/fundamentals/active-directory-data-storage-eu.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Administrators can choose to enable or disable certain Azure AD features. If the
7979

8080
* **Azure Active Directory Multi Tenant Collaboration** - With multi tenant collaboration scenarios enabled, customers can configure their tenant to collaborate with users from a different tenant. For example, a customer can invite users to their tenant in a B2B context. A customer can create a multi-tenant SaaS application that allows other third party tenants to provision the application in the third party tenant. Or, the customer can make two or more tenants affiliated with one another and act as a single tenant in certain scenarios, such as multi-tenant organization (MTO) formation, tenant to tenant sync, and shared e-mail domain sharing. Customer configuration and use of multi tenant collaboration may occur with tenants outside of the EU Data Residency and EU Data Boundary resulting in some customer data, such as user and device account data, usage data, and service configuration (application, policy, and group) stored and processed in the location of the collaborating tenant.
8181
* **Application Proxy** - Allows customers to access their on-premises web applications externally. Customers may choose advanced routing configurations that allow customer data to egress outside of the EU Data Residency and EU Data Boundary, including user account data, usage data, and application configuration data.
82-
* **Microsoft 365 Multi Geo** - Microsoft 365 Multi-Geo provides customers with the ability to expand their Microsoft 365 presence to multiple geographic regions/countries within a single existing Microsoft 365 tenant. Azure Active Directory will egress customer data to perform backup authentication to the locations configured by the customer. Types of customer data include user and device account data, branding data, and service configuration data (application, policy, and group).
82+
* **Microsoft 365 Multi Geo** - Microsoft 365 Multi-Geo provides customers with the ability to expand their Microsoft 365 presence to multiple geographic countries/regions within a single existing Microsoft 365 tenant. Azure Active Directory will egress customer data to perform backup authentication to the locations configured by the customer. Types of customer data include user and device account data, branding data, and service configuration data (application, policy, and group).
8383

8484
### Other EU Data Boundary online services
8585

articles/active-directory/hybrid/how-to-connect-health-agent-install.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -319,7 +319,7 @@ To configure the Azure AD Connect Health agent to use an HTTP proxy, you can:
319319
> [!NOTE]
320320
> To update the proxy settings, you must restart all Azure AD Connect Health agent services. Run the following command:
321321
>
322-
> `Restart-Service AzureADConnectHealth*`
322+
> `Restart-Service AdHealthAdfs*`
323323
324324
#### Import existing proxy settings
325325

0 commit comments

Comments
 (0)