Skip to content

Commit 5a32514

Browse files
TaojunshenTaojunshen
authored
Merge pull request #250911 from MicrosoftDocs/main
9/11/2023 AM Publish
2 parents d34c839 + cefdb2e commit 5a32514

File tree

141 files changed

+1478
-4734
lines changed

Some content is hidden

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

141 files changed

+1478
-4734
lines changed

‎.openpublishing.redirection.json

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23402,6 +23402,111 @@
2340223402
"redirect_url": "/entra/msal/python/advanced/msal-python-token-cache-serialization",
2340323403
"redirect_document_id": false
2340423404
},
23405+
{
23406+
"source_path_from_root": "/articles/active-directory/develop/msal-python-adfs-support.md",
23407+
"redirect_url": "/entra/msal/python/advanced/msal-python-adfs-support",
23408+
"redirect_document_id": false
23409+
},
23410+
{
23411+
"source_path_from_root": "/articles/active-directory/develop/msal-error-handling-dotnet.md",
23412+
"redirect_url": "/entra/msal/dotnet/advanced/exceptions/msal-error-handling",
23413+
"redirect_document_id": false
23414+
},
23415+
{
23416+
"source_path_from_root": "/articles/active-directory/develop/msal-logging-dotnet.md",
23417+
"redirect_url": "/entra/msal/dotnet/advanced/exceptions/msal-logging",
23418+
"redirect_document_id": false
23419+
},
23420+
{
23421+
"source_path_from_root": "/articles/active-directory/develop/msal-net-acquire-token-silently.md",
23422+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/acquire-token-silently",
23423+
"redirect_document_id": false
23424+
},
23425+
{
23426+
"source_path_from_root": "/articles/active-directory/develop/msal-net-adfs-support.md",
23427+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/desktop-mobile/adfs-support",
23428+
"redirect_document_id": false
23429+
},
23430+
{
23431+
"source_path_from_root": "/articles/active-directory/develop/msal-net-b2c-considerations.md",
23432+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/desktop-mobile/social-identities",
23433+
"redirect_document_id": false
23434+
},
23435+
{
23436+
"source_path_from_root": "/articles/active-directory/develop/msal-net-clear-token-cache.md",
23437+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/clear-token-cache",
23438+
"redirect_document_id": false
23439+
},
23440+
{
23441+
"source_path_from_root": "/articles/active-directory/develop/msal-net-client-assertions.md",
23442+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/msal-net-client-assertions",
23443+
"redirect_document_id": false
23444+
},
23445+
{
23446+
"source_path_from_root": "/articles/active-directory/develop/msal-net-differences-adal-net.md",
23447+
"redirect_url": "/entra/msal/dotnet/how-to/differences-adal-msal-net",
23448+
"redirect_document_id": false
23449+
},
23450+
{
23451+
"source_path_from_root": "/articles/active-directory/develop/msal-net-initializing-client-applications.md",
23452+
"redirect_url": "/entra/msal/dotnet/getting-started/initializing-client-applications",
23453+
"redirect_document_id": false
23454+
},
23455+
{
23456+
"source_path_from_root": "/articles/active-directory/develop/msal-net-instantiate-confidential-client-config-options.md",
23457+
"redirect_url": "/entra/msal/dotnet/getting-started/instantiate-confidential-client-config-options",
23458+
"redirect_document_id": false
23459+
},
23460+
{
23461+
"source_path_from_root": "/articles/active-directory/develop/msal-net-instantiate-public-client-config-options.md",
23462+
"redirect_url": "/entra/msal/dotnet/getting-started/instantiate-public-client-config-options",
23463+
"redirect_document_id": false
23464+
},
23465+
{
23466+
"source_path_from_root": "/articles/active-directory/develop/msal-net-migration-confidential-client.md",
23467+
"redirect_url": "/entra/msal/dotnet/how-to/migrate-confidential-client",
23468+
"redirect_document_id": false
23469+
},
23470+
{
23471+
"source_path_from_root": "/articles/active-directory/develop/msal-net-migration-public-client.md",
23472+
"redirect_url": "/entra/msal/dotnet/how-to/migrate-public-client",
23473+
"redirect_document_id": false
23474+
},
23475+
{
23476+
"source_path_from_root": "/articles/active-directory/develop/msal-net-provide-httpclient.md",
23477+
"redirect_url": "/entra/msal/dotnet/advanced/httpclient",
23478+
"redirect_document_id": false
23479+
},
23480+
{
23481+
"source_path_from_root": "/articles/active-directory/develop/msal-net-token-cache-serialization.md",
23482+
"redirect_url": "/entra/msal/dotnet/how-to/token-cache-serialization",
23483+
"redirect_document_id": false
23484+
},
23485+
{
23486+
"source_path_from_root": "/articles/active-directory/develop/msal-net-user-gets-consent-for-multiple-resources.md",
23487+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/user-gets-consent-for-multiple-resources",
23488+
"redirect_document_id": false
23489+
},
23490+
{
23491+
"source_path_from_root": "/articles/active-directory/develop/msal-net-uwp-considerations.md",
23492+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/desktop-mobile/uwp",
23493+
"redirect_document_id": false
23494+
},
23495+
{
23496+
"source_path_from_root": "/articles/active-directory/develop/msal-net-web-browsers.md",
23497+
"redirect_url": "/entra/msal/dotnet/acquiring-tokens/using-web-browsers",
23498+
"redirect_document_id": false
23499+
},
23500+
{
23501+
"source_path_from_root": "/articles/active-directory/develop/msal-net-migration.md",
23502+
"redirect_url": "/entra/msal/dotnet/how-to/msal-net-migration",
23503+
"redirect_document_id": false
23504+
},
23505+
{
23506+
"source_path_from_root": "/articles/active-directory/develop/microsoft-identity-web.md",
23507+
"redirect_url": "/entra/msal/dotnet/microsoft-identity-web/",
23508+
"redirect_document_id": false
23509+
},
2340523510
{
2340623511
"source_path_from_root": "/articles/networking/azure-orbital-overview.md",
2340723512
"redirect_url": "/azure/orbital/overview",

‎articles/active-directory-b2c/add-ropc-policy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ zone_pivot_groups: b2c-policy-type
2222

2323
In Azure Active Directory B2C (Azure AD B2C), the resource owner password credentials (ROPC) flow is an OAuth standard authentication flow. In this flow, an application, also known as the relying party, exchanges valid credentials for tokens. The credentials include a user ID and password. The tokens returned are an ID token, access token, and a refresh token.
2424

25+
> [!WARNING]
26+
> We recommend that you _don't_ use the ROPC flow. In most scenarios, more secure alternatives are available and recommended. This flow requires a very high degree of trust in the application and carries risks that aren't present in other flows. You should only use this flow when other more secure flows aren't viable.
27+
2528
## ROPC flow notes
2629

2730
In Azure Active Directory B2C (Azure AD B2C), the following options are supported:

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

Lines changed: 4 additions & 3 deletions
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/22/2023
10+
ms.date: 09/08/2023
1111

1212
ms.author: justinha
1313
author: mjsantani
@@ -74,8 +74,9 @@ In addition to choosing who can be nudged, you can define how many days a user c
7474

7575
To enable a registration campaign in the Azure portal, complete the following steps:
7676

77-
1. In the Azure portal, click **Security** > **Authentication methods** > **Registration campaign**.
78-
1. For **State**, click **Microsoft managed** or **Enabled**. In the following screenshot, the registration campaign is **Microsoft managed**. That setting allows Microsoft to set the default value to be either enabled or disabled. For the registration campaign, the Microsoft managed value is Enabled for voice call and SMS users with free and trial subscriptions. For more information, see [Protecting authentication methods in Azure Active Directory](concept-authentication-default-enablement.md).
77+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Authentication Policy Administrator](../roles/permissions-reference.md#authentication-policy-administrator).
78+
1. Browse to **Protection** > **Authentication methods** > **Registration campaign**.
79+
1. For **State**, click **Microsoft managed** or **Enabled**. In the following screenshot, the registration campaign is **Microsoft managed**. That setting allows Microsoft to set the default value to be either Enabled or Disabled. For the registration campaign, the Microsoft managed value is Enabled for voice call and text message users with free and trial subscriptions. For more information, see [Protecting authentication methods in Azure Active Directory](concept-authentication-default-enablement.md).
7980

8081
![Screenshot of enabling a registration campaign.](./media/how-to-nudge-authenticator-app/registration-campaign.png)
8182

‎articles/active-directory/cloud-infrastructure-entitlement-management/product-rule-based-anomalies.md

Lines changed: 20 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Create and view rule-based anomalies and anomaly triggers in Permissions Management
3-
description: How to create and view rule-based anomalies and anomaly triggers in Permissions Management.
2+
title: Create and view rule-based anomaly alerts and alert triggers in Permissions Management
3+
description: How to create and view rule-based anomaly alerts and alert triggers in Permissions Management.
44
services: active-directory
55
author: jenniferf-skc
66
manager: amycolannino
@@ -12,13 +12,20 @@ ms.date: 02/23/2022
1212
ms.author: jfields
1313
---
1414

15-
# Create and view rule-based anomaly alerts and anomaly triggers
15+
# Create and view rule-based anomaly alerts and alert triggers
1616

17-
Rule-based anomalies identify recent activity in Permissions Management that is determined to be unusual based on explicit rules defined in the activity trigger. The goal of rule-based anomaly is high precision detection.
17+
Rule-based anomalies identify recent activity in Permissions Management that is determined to be unusual based on explicit rules defined in the alert trigger. The goal of rule-based anomaly alerts is high-precision detection.
18+
19+
You can configure rule-based anomaly alert triggers for the following conditions:
20+
- **Any Resource Accessed for the First Time**: The identity accesses a resource for the first time during the specified time interval.
21+
- **Identity Performs a Particular Task for the First Time**: The identity does a specific task for the first time during the specified time interval.
22+
- **Identity Performs a Task for the First Time**: The identity performs any task for the first time during the specified time interval.
23+
24+
Alert triggers are based on data collected. All alerts, if triggered, are shown every hour under the Alerts subtab.
1825

1926
## View rule-based anomaly alerts
2027

21-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
28+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
2229
1. Select **Rule-Based Anomaly**, and then select the **Alerts** subtab.
2330

2431
The **Alerts** subtab displays the following information:
@@ -49,11 +56,11 @@ Rule-based anomalies identify recent activity in Permissions Management that is
4956
- **Details**: Displays details about **Authorization System Type**, **Authorization Systems**, **Resources**, **Tasks**, **Identities**, and **Activity**
5057
- **Activity**: Displays details about the **Identity Name**, **Resource Name**, **Task Name**, **Date/Time**, **Inactive For**, and **IP Address**. Selecting the "eye" icon displays the **Raw Events Summary**
5158

52-
## Create a rule-based anomaly trigger
59+
## Create a rule-based anomaly alert trigger
5360

54-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
61+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
5562
1. Select **Rule-Based Anomaly**, and then select the **Alerts** subtab.
56-
1. Select **Create Anomaly Trigger**.
63+
1. Select **Create Alert Trigger**.
5764

5865
1. In the **Alert Name** box, enter a name for the alert.
5966
1. Select the **Authorization System**, **AWS**, **Azure**, or **GCP**.
@@ -72,9 +79,9 @@ Rule-based anomalies identify recent activity in Permissions Management that is
7279
1. On the **Configuration** tab, to update the **Time Interval**, select **90 Days**, **60 Days**, or **30 Days** from the **Time range** dropdown.
7380
1. Select **Save**.
7481

75-
## View a rule-based anomaly trigger
82+
## View a rule-based anomaly alert trigger
7683

77-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
84+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
7885
1. Select **Rule-Based Anomaly**, and then select the **Alert Triggers** subtab.
7986

8087
The **Alert Triggers** subtab displays the following information:
@@ -113,7 +120,7 @@ Rule-based anomalies identify recent activity in Permissions Management that is
113120

114121
## Next steps
115122

116-
- For an overview on activity triggers, see [View information about activity triggers](ui-triggers.md).
123+
- For an overview on alerts and alert triggers, see [View information about alerts and alert triggers](ui-triggers.md).
117124
- For information on activity alerts and alert triggers, see [Create and view activity alerts and alert triggers](how-to-create-alert-trigger.md).
118-
- For information on finding outliers in identity's behavior, see [Create and view statistical anomalies and anomaly triggers](product-statistical-anomalies.md).
119-
- For information on permission analytics triggers, see [Create and view permission analytics triggers](product-permission-analytics.md).
125+
- For information on finding outliers in identity's behavior, see [Create and view statistical anomaly alerts and alert triggers](product-statistical-anomalies.md).
126+
- For information on permission analytics alerts and alert triggers, see [Create and view permission analytics alerts and alert triggers](product-permission-analytics.md).

‎articles/active-directory/develop/TOC.yml

Lines changed: 8 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -643,6 +643,8 @@
643643
- name: National clouds and MSAL
644644
displayName: china, germany, gov, 21vianet
645645
href: msal-national-cloud.md
646+
- name: Application configuration
647+
href: msal-client-application-configuration.md
646648
- name: MSAL Android
647649
items:
648650
- name: Library initialization
@@ -748,66 +750,12 @@
748750
href: msal-js-known-issues-ie-edge-browsers.md
749751
- name: MSAL.NET
750752
displayName: ASP.NET Core, Xamarin
751-
items:
752-
- name: Library initialization
753-
items:
754-
- name: Microsoft.Identity.Web (MSAL wrapper)
755-
displayName: auth, library, .NET Core, msal
756-
href: microsoft-identity-web.md
757-
- name: Application configuration
758-
href: msal-client-application-configuration.md
759-
- name: Application initialization
760-
href: msal-net-initializing-client-applications.md
761-
- name: Confidential client instantiation
762-
href: msal-net-instantiate-confidential-client-config-options.md
763-
- name: Confidential client credentials (cert, secret, assertion)
764-
displayName: certificate
765-
href: msal-net-client-assertions.md
766-
- name: Public client instantiation
767-
href: msal-net-instantiate-public-client-config-options.md
768-
- name: Instantiation with custom HttpClient
769-
href: msal-net-provide-httpclient.md
770-
- name: Web browser interaction (system and embedded)
771-
href: msal-net-web-browsers.md
772-
- name: Universal Windows Platform
773-
href: msal-net-uwp-considerations.md
774-
- name: Authentication and single sign-on (SSO)
775-
displayName: caching, token caching, caching tokens
776-
items:
777-
- name: Get a token from the cache
778-
displayName: acquire access token
779-
href: msal-net-acquire-token-silently.md
780-
- name: Clear the token cache
781-
href: msal-net-clear-token-cache.md
782-
- name: Serialize the token cache
783-
displayName: serialization
784-
href: msal-net-token-cache-serialization.md
785-
- name: Get consent for several resources
786-
href: msal-net-user-gets-consent-for-multiple-resources.md
787-
- name: Connections and integrations
788-
items:
789-
- name: Integrate with AD FS
790-
href: msal-net-adfs-support.md
791-
- name: Integrate with Azure AD B2C
792-
href: msal-net-b2c-considerations.md
793-
- name: Logging and error handling
794-
displayName: MSAL.NET
795-
items:
796-
- name: Handle errors and exceptions in MSAL.NET
797-
displayName: handling, catch
798-
href: msal-error-handling-dotnet.md
799-
- name: Logging in MSAL.NET
800-
href: msal-logging-dotnet.md
801-
- name: Migration to MSAL.NET
802-
items:
803-
- name: Migrate from ADAL.NET to MSAL.NET
804-
href: msal-net-migration.md
805-
- name: Migrate confidential client apps to MSAL.NET
806-
href: msal-net-migration-confidential-client.md
807-
- name: Migrate public client apps to MSAL.NET
808-
href: msal-net-migration-public-client.md
809-
- name: Differences between ADAL.NET and MSAL.NET
810-
href: msal-net-differences-adal-net.md
753+
href: /entra/msal/dotnet
754+
- name: Microsoft.Identity.Web (MSAL wrapper)
755+
displayName: auth, library, .NET Core, msal
756+
href: /entra/msal/dotnet/microsoft-identity-web/
757+
- name: Application configuration
758+
href: msal-client-application-configuration.md
811759
- name: MSAL Node
812760
displayName: Node.js
813761
items:

‎articles/active-directory/develop/certificate-credentials.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.subservice: develop
1010
ms.workload: identity
11-
ms.topic: conceptual
11+
ms.topic: reference
1212
ms.date: 02/27/2023
1313
ms.author: owenrichards
1414
ms.reviewer: kenwith

‎articles/active-directory/develop/custom-claims-provider-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.subservice: develop
1111
ms.workload: identity
12-
ms.topic: conceptual
12+
ms.topic: reference
1313
ms.date: 03/06/2023
1414
ms.author: davidmu
1515
ms.reviewer: jassuri

0 commit comments

Comments
 (0)