Skip to content

Commit 2b2c8cf

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-toc1
2 parents cb5849e + cd6cb03 commit 2b2c8cf

File tree

105 files changed

+654
-433
lines changed

Some content is hidden

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

105 files changed

+654
-433
lines changed

.openpublishing.redirection.defender-for-iot.json

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,16 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/resources-training-sessions.md",
5+
"redirect_url": "https://techcommunity.microsoft.com/t5/microsoft-defender-for-iot-blog/microsoft-defender-for-iot-ninja-training/ba-p/2428899",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-manage-the-alert-event.md",
510
"redirect_url": "/azure/defender-for-iot/organizations/how-to-view-alerts",
611
"redirect_document_id": false
712
},
8-
{
9-
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-install-software.md",
13+
{ "source_path_from_root": "/articles/defender-for-iot/organizations/how-to-install-software.md",
1014
"redirect_url": "/azure/defender-for-iot/organizations/ot-deploy/install-software-ot-sensor",
1115
"redirect_document_id": false
1216
},

articles/active-directory-b2c/saml-identity-provider-technical-profile.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 01/11/2022
12+
ms.date: 01/05/2023
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -31,7 +31,7 @@ Each SAML identity provider has different steps to expose and set the service pr
3131
The following example shows a URL address to the SAML metadata of an Azure AD B2C technical profile:
3232

3333
```
34-
https://your-tenant-name.b2clogin.com/your-tenant-name/your-policy/samlp/metadata?idptp=your-technical-profile
34+
https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/your-policy/samlp/metadata?idptp=your-technical-profile
3535
```
3636

3737
Replace the following values:

articles/active-directory/authentication/how-to-mfa-registration-campaign.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: active-directory
77
ms.subservice: authentication
88
ms.custom: ignite-2022
99
ms.topic: conceptual
10-
ms.date: 06/23/2022
10+
ms.date: 01/05/2023
1111

1212
ms.author: justinha
1313
author: mjsantani
@@ -305,6 +305,9 @@ Yes. If they have been scoped for the nudge using the policy.
305305

306306
It's the same as snoozing.
307307

308+
**Why don’t some users see a nudge when there is a conditional access policy for "Register security information"?**
309+
310+
A nudge won't appear if a user is in scope for a conditional access policy that blocks access to the **Register security information** page.
308311

309312
## Next steps
310313

articles/active-directory/authentication/troubleshoot-sspr-writeback.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: authentication
88
ms.topic: troubleshooting
9-
ms.date: 02/22/2022
9+
ms.date: 01/05/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -157,7 +157,7 @@ The following more specific issues may occur with password writeback. If you hav
157157
| Federated, pass-through authentication, or password-hash-synchronized users who attempt to reset their passwords, see an error after they submit their password. The error indicates that there was a service problem. <br> <br> In addition to this problem, during password reset operations, you might see an error in your event logs from the Azure AD Connect service indicating an "Object could not be found" error. | This error usually indicates that the sync engine is unable to find either the user object in the Azure AD connector space or the linked metaverse (MV) or Azure AD connector space object. <br> <br> To troubleshoot this problem, make sure that the user is indeed synchronized from on-premises to Azure AD via the current instance of Azure AD Connect and inspect the state of the objects in the connector spaces and MV. Confirm that the Active Directory Certificate Services (AD CS) object is connected to the MV object via the "Microsoft.InfromADUserAccountEnabled.xxx" rule.|
158158
| Federated, pass-through authentication, or password-hash-synchronized users who attempt to reset their passwords see an error after they submit their password. The error indicates that there was a service problem. <br> <br> In addition to this problem, during password reset operations, you might see an error in your event logs from the Azure AD Connect service that indicates that there's a "Multiple matches found" error. | This indicates that the sync engine detected that the MV object is connected to more than one AD CS object via "Microsoft.InfromADUserAccountEnabled.xxx". This means that the user has an enabled account in more than one forest. This scenario isn't supported for password writeback. |
159159
| Password operations fail with a configuration error. The application event log contains Azure AD Connect error 6329 with the text "0x8023061f (The operation failed because password synchronization is not enabled on this Management Agent)". | This error occurs if the Azure AD Connect configuration is changed to add a new Active Directory forest (or to remove and readd an existing forest) after the password writeback feature has already been enabled. Password operations for users in these recently added forests fail. To fix the problem, disable and then re-enable the password writeback feature after the forest configuration changes have been completed.
160-
| SSPR_0029: We are unable to reset your password due to an error in your on-premises configuration. Please contact your admin and ask them to investigate. | Problem: Password writeback has been enabled following all of the required steps, but when attempting to change a password you receive "SSPR_0029: Your organization hasn’t properly set up the on-premises configuration for password reset." Checking the event logs on the Azure AD Connect system shows that the management agent credential was denied access.Possible Solution: Use RSOP on the Azure AD Connect system and your domain controllers to see if the policy "Network access: Restrict clients allowed to make remote calls to SAM" found under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options is enabled. Edit the policy to include the MSOL_XXXXXXX management account as an allowed user. |
160+
| SSPR_0029: We are unable to reset your password due to an error in your on-premises configuration. Please contact your admin and ask them to investigate. | Problem: Password writeback has been enabled following all of the required steps, but when attempting to change a password you receive "SSPR_0029: Your organization hasn’t properly set up the on-premises configuration for password reset." Checking the event logs on the Azure AD Connect system shows that the management agent credential was denied access.Possible Solution: Use RSOP on the Azure AD Connect system and your domain controllers to see if the policy "Network access: Restrict clients allowed to make remote calls to SAM" found under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options is enabled. Edit the policy to include the MSOL_XXXXXXX management account as an allowed user. For more information, see [Troubleshoot error SSPR_0029: Your organization hasn't properly set up the on-premises configuration for password reset](/troubleshoot/azure/active-directory/password-writeback-error-code-sspr-0029).|
161161

162162
## Password writeback event log error codes
163163

articles/active-directory/conditional-access/workload-identity.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,18 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: how-to
9-
ms.date: 11/21/2022
9+
ms.date: 01/05/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
1313
manager: amycolannino
14-
ms.reviewer: dawoo
14+
ms.reviewer: swethar
1515

1616
ms.collection: M365-identity-device-management
1717
---
1818
# Conditional Access for workload identities
1919

20-
Conditional Access policies have historically applied only to users when they access apps and services like SharePoint online or the Azure portal. We are now extending support for Conditional Access policies to be applied to service principals owned by the organization. We call this capability Conditional Access for workload identities.
20+
Conditional Access policies have historically applied only to users when they access apps and services like SharePoint online or the Azure portal. We're now extending support for Conditional Access policies to be applied to service principals owned by the organization. We call this capability Conditional Access for workload identities.
2121

2222
A [workload identity](../develop/workload-identities-overview.md) is an identity that allows an application or service principal access to resources, sometimes in the context of a user. These workload identities differ from traditional user accounts as they:
2323

@@ -28,7 +28,8 @@ A [workload identity](../develop/workload-identities-overview.md) is an identity
2828
These differences make workload identities harder to manage and put them at higher risk for compromise.
2929

3030
> [!IMPORTANT]
31-
> Conditional Access policies can be scoped to service principals in Azure AD with Workload Identities Premium licenses.
31+
> Workload Identities Premium licenses are required to create or modify Conditional Access policies scoped to service principals.
32+
> In directories without appropriate licenses, Conditional Access policies created prior to the release of Workload Identities Premium will be available for deletion only.
3233
3334
> [!NOTE]
3435
> Policy can be applied to single tenant service principals that have been registered in your tenant. Third party SaaS and multi-tenanted apps are out of scope. Managed identities are not covered by policy.

articles/active-directory/develop/howto-configure-publisher-domain.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,26 @@
22
title: Configure an app's publisher domain
33
description: Learn how to configure an app's publisher domain to let users know where their information is being sent.
44
services: active-directory
5-
author: rwike77
5+
author: OwenRichards1
66
manager: CelesteDG
77

88
ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: how-to
1111
ms.workload: identity
12-
ms.date: 11/11/2022
13-
ms.author: ryanwi
12+
ms.date: 01/05/2023
13+
ms.author: owenrichards
1414
ms.reviewer: xurobert, brianokoyo
1515
ms.custom: contperf-fy21q4, aaddev
1616
---
1717

1818
# Configure an app's publisher domain
1919

20-
An app’s publisher domain informs users where their information is being sent. The publisher domain also acts as an input or prerequisite for [publisher verification](publisher-verification-overview.md).
20+
An app’s publisher domain informs users where their information is being sent. The publisher domain also acts as an input or prerequisite for [publisher verification](publisher-verification-overview.md). Depending on when the app was registered and the status of the Publisher Verification, it would be displayed directly to the user on the [application's consent prompt](application-consent-experience.md). An application’s publisher domain is displayed to users (depending on the state of Publisher Verification) on the consent UX to let users know where their information is being sent for trustworthiness.
2121

22-
In an app's [consent prompt](application-consent-experience.md), either the publisher domain or the publisher verification status appears. Which information is shown depends on whether the app is a [multitenant app](/azure/architecture/guide/multitenant/overview), when the app was registered, and the app's publisher verification status.
22+
In an app's consent prompt, either the publisher domain or the publisher verification status appears. Which information is shown depends on whether the app is a [multitenant app](/azure/architecture/guide/multitenant/overview), when the app was registered, and the app's publisher verification status.
23+
24+
## Understand multitenant apps
2325

2426
A *multitenant app* is an app that supports user accounts that are outside a single organizational directory. For example, a multitenant app might support all Azure Active Directory (Azure AD) work or school accounts, or it might support both Azure AD work or school accounts and personal Microsoft accounts.
2527

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

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory
55
author: henrymbuguakiarie
66
manager: CelesteDG
77

8-
ms.date: 12/01/2022
8+
ms.date: 01/05/2023
99
ms.service: active-directory
1010
ms.subservice: develop
1111
ms.topic: reference
@@ -18,6 +18,23 @@ ms.custom: has-adal-ref
1818

1919
Welcome to what's new in the Microsoft identity platform documentation. This article lists new docs that have been added and those that have had significant updates in the last three months.
2020

21+
## December 2022
22+
23+
### New articles
24+
25+
- [Block workload identity federation on managed identities using a policy](workload-identity-federation-block-using-azure-policy.md)
26+
- [Troubleshooting the configured permissions limits](troubleshoot-required-resource-access-limits.md)
27+
28+
### Updated articles
29+
30+
- [Quickstart: Protect an ASP.NET Core web API with the Microsoft identity platform](quickstart-v2-aspnet-core-web-api.md)
31+
- [Quickstart: Get a token and call the Microsoft Graph API by using a console app's identity](quickstart-v2-netcore-daemon.md)
32+
- [Tutorial: Sign in users and call a protected API from a Blazor WebAssembly app](tutorial-blazor-webassembly.md)
33+
- [A web API that calls web APIs: Code configuration](scenario-web-api-call-api-app-configuration.md)
34+
- [Web app that signs in users: Code configuration](scenario-web-app-sign-user-app-configuration.md)
35+
- [Web app that signs in users: App registration](scenario-web-app-sign-user-app-registration.md)
36+
- [Microsoft identity platform docs: What's new](whats-new-docs.md)
37+
- [Tutorial: Create a Blazor Server app that uses the Microsoft identity platform for authentication](tutorial-blazor-server.md)
2138
## November 2022
2239

2340
### New articles
@@ -57,16 +74,3 @@ Welcome to what's new in the Microsoft identity platform documentation. This art
5774
- [Quickstart: Register an application with the Microsoft identity platform](quickstart-register-app.md)
5875
- [Tutorial: Sign in users and call the Microsoft Graph API from a JavaScript single-page application](tutorial-v2-javascript-spa.md)
5976
- [Tutorial: Sign in users and call the Microsoft Graph API from a React single-page app (SPA) using auth code flow](tutorial-v2-react.md)
60-
61-
## September 2022
62-
63-
### New articles
64-
65-
- [Configure a user-assigned managed identity to trust an external identity provider (preview)](workload-identity-federation-create-trust-user-assigned-managed-identity.md)
66-
- [Important considerations and restrictions for federated identity credentials](workload-identity-federation-considerations.md)
67-
68-
### Updated articles
69-
70-
- [How to use Continuous Access Evaluation enabled APIs in your applications](app-resilience-continuous-access-evaluation.md)
71-
- [Run automated integration tests](test-automate-integration-testing.md)
72-
- [Tutorial: Sign in users and call the Microsoft Graph API from a JavaScript single-page application (SPA)](tutorial-v2-javascript-spa.md)

articles/active-directory/external-identities/whats-new-docs.md

Lines changed: 9 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,15 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory External Identities 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 External Identities service, see [What's new in Azure Active Directory](../fundamentals/whats-new.md).
1717

18+
## December 2022
19+
20+
### Updated articles
21+
22+
- [Azure Active Directory B2B collaboration invitation redemption](redemption-experience.md)
23+
- [Azure Active Directory B2B collaboration API and customization](customize-invitation-api.md)
24+
- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
25+
- [Auditing and reporting a B2B collaboration user](auditing-and-reporting.md)
26+
1827
## November 2022
1928

2029
### Updated articles
@@ -45,22 +54,3 @@ Welcome to what's new in Azure Active Directory External Identities documentatio
4554
- [Configure Microsoft cloud settings for B2B collaboration (Preview)](cross-cloud-settings.md)
4655
- [Add Microsoft account (MSA) as an identity provider for External Identities](microsoft-account.md)
4756
- [How users in your organization can invite guest users to an app](add-users-information-worker.md)
48-
49-
## September 2022
50-
51-
### Updated articles
52-
53-
- [Self-service sign-up](self-service-sign-up-overview.md)
54-
- [Properties of an Azure Active Directory B2B collaboration user](user-properties.md)
55-
- [Azure Active Directory (Azure AD) identity provider for External Identities](azure-ad-account.md)
56-
- [Add Google as an identity provider for B2B guest users](google-federation.md)
57-
- [Email one-time passcode authentication](one-time-passcode.md)
58-
- [Add B2B collaboration guest users without an invitation link or email](add-user-without-invite.md)
59-
- [Identity Providers for External Identities](identity-providers.md)
60-
- [Tutorial: Use PowerShell to bulk invite Azure AD B2B collaboration users](bulk-invite-powershell.md)
61-
- [B2B collaboration user claims mapping in Azure Active Directory](claims-mapping.md)
62-
- [Azure Active Directory External Identities: What's new](whats-new-docs.md)
63-
- [Azure Active Directory B2B collaboration invitation redemption](redemption-experience.md)
64-
- [Add Azure Active Directory B2B collaboration users in the Azure portal](add-users-administrator.md)
65-
- [Leave an organization as an external user](leave-the-organization.md)
66-
- [Grant B2B users in Azure AD access to your on-premises applications](hybrid-cloud-to-on-premises.md)

articles/active-directory/manage-apps/whats-new-docs.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory application management"
33
description: "New and updated documentation for the Azure Active Directory application management."
4-
ms.date: 12/01/2022
4+
ms.date: 01/05/2023
55
ms.service: active-directory
66
ms.subservice: app-mgmt
77
ms.topic: reference
@@ -15,6 +15,20 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory (Azure AD) application management 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 application management service, see [What's new in Azure AD](../fundamentals/whats-new.md).
1717

18+
## December 2022
19+
20+
### Updated articles
21+
22+
- [Grant consent on behalf of a single user by using PowerShell](grant-consent-single-user.md)
23+
- [Tutorial: Configure F5 BIG-IP SSL-VPN for Azure AD SSO](f5-aad-password-less-vpn.md)
24+
- [Integrate F5 BIG-IP with Azure Active Directory](f5-aad-integration.md)
25+
- [Azure Active Directory application management: What's new](whats-new-docs.md)
26+
- [Deploy F5 BIG-IP Virtual Edition VM in Azure](f5-bigip-deployment-guide.md)
27+
- [End-user experiences for applications](end-user-experiences.md)
28+
- [Tutorial: Migrate your applications from Okta to Azure Active Directory](migrate-applications-from-okta-to-azure-active-directory.md)
29+
- [Tutorial: Configure F5 BIG-IP Access Policy Manager for Kerberos authentication](f5-big-ip-kerberos-advanced.md)
30+
- [Tutorial: Configure F5 BIG-IP Easy Button for Kerberos single sign-on](f5-big-ip-kerberos-easy-button.md)
31+
- [Tutorial: Configure F5 BIG-IP Easy Button for header-based and LDAP single sign-on](f5-big-ip-ldap-header-easybutton.md)
1832
## November 2022
1933

2034
### Updated articles
@@ -35,15 +49,3 @@ Welcome to what's new in Azure Active Directory (Azure AD) application managemen
3549
- [Tutorial: Configure F5 BIG-IP Easy Button for header-based and LDAP single sign-on](f5-big-ip-ldap-header-easybutton.md)
3650
- [Tutorial: Migrate your applications from Okta to Azure Active Directory](migrate-applications-from-okta-to-azure-active-directory.md)
3751
- [Tutorial: Configure Secure Hybrid Access with Azure Active Directory and Silverfort](silverfort-azure-ad-integration.md)
38-
39-
## September 2022
40-
41-
### New articles
42-
43-
- [Tutorial: Configure Datawiza to enable Azure Active Directory Multi-Factor Authentication and single sign-on to Oracle PeopleSoft](datawiza-azure-ad-sso-oracle-peoplesoft.md)
44-
- [SAML Request Signature Verification (Preview)](howto-enforce-signed-saml-authentication.md)
45-
46-
### Updated articles
47-
48-
- [Manage app consent policies](manage-app-consent-policies.md)
49-
- [Unexpected consent prompt when signing in to an application](application-sign-in-unexpected-user-consent-prompt.md)

0 commit comments

Comments
 (0)