Skip to content

Commit d306396

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into multir
2 parents f478418 + 438adb2 commit d306396

File tree

1,334 files changed

+7280
-5224
lines changed

Some content is hidden

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

1,334 files changed

+7280
-5224
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,11 @@
3030
"redirect_url": "/azure/active-directory/saas-apps/tutorial-list",
3131
"redirect_document_id": false
3232
},
33+
{
34+
"source_path_from_root": "/articles/active-directory/fundamentals/whats-new-microsoft-365-government.md",
35+
"redirect_url": "/azure/active-directory/fundamentals/whats-new",
36+
"redirect_document_id": true
37+
},
3338
{
3439
"source_path_from_root": "/articles/active-directory/manage-apps/common-scenarios.md",
3540
"redirect_url": "/azure/active-directory/manage-apps/what-is-application-management",

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -415,6 +415,11 @@
415415
"source_path_from_root": "/articles/azure-monitor/insights/cosmosdb-insights-overview.md" ,
416416
"redirect_url": "/azure/cosmos-db/cosmosdb-insights-overview",
417417
"redirect_document_id": false
418+
},
419+
{
420+
"source_path_from_root": "/articles/azure-monitor/insights/network-insights-overview.md" ,
421+
"redirect_url": "/azure/network-watcher/network-insights-overview",
422+
"redirect_document_id": false
418423
}
419424
]
420425
}

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40312,6 +40312,11 @@
4031240312
"source_path_from_root": "/articles/virtual-machines/windows/winrm.md",
4031340313
"redirect_url": "/azure/virtual-machines/windows/connect-winrm",
4031440314
"redirect_document_id": false
40315+
},
40316+
{
40317+
"source_path_from_root": "/articles/applied-ai-services/form-recognizer/tutorial-ai-builder.md",
40318+
"redirect_url": "https://docs.microsoft.com/ai-builder/create-form-processing-model",
40319+
"redirect_document_id": false
4031540320
}
4031640321
]
4031740322
}

articles/active-directory-b2c/best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,4 +87,4 @@ Stay up to date with the state of the service and find support options.
8787
|--|--|
8888
| [Service updates](https://azure.microsoft.com/updates/?product=active-directory-b2c) | Stay up to date with Azure AD B2C product updates and announcements. |
8989
| [Microsoft Support](support-options.md) | File a support request for Azure AD B2C technical issues. Billing and subscription management support is provided at no cost. |
90-
| [Azure status](https://status.azure.com/status) | View the current health status of all Azure services. |
90+
| [Azure status](https://azure.status.microsoft/status) | View the current health status of all Azure services. |

articles/active-directory-b2c/custom-domain.md

Lines changed: 10 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: how-to
12-
ms.date: 05/13/2022
12+
ms.date: 07/26/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
ms.custom: "b2c-support"
@@ -116,13 +116,21 @@ Follow these steps to create an Azure Front Door:
116116
|Tier| Select either Standard or Premium tier. Standard tier is content delivery optimized. Premium tier builds on Standard tier and is focused on security. See [Tier Comparison](../frontdoor/standard-premium/tier-comparison.md).|
117117
|Endpoint name| Enter a globally unique name for your endpoint, such as `b2cazurefrontdoor`. The **Endpoint hostname** is generated automatically. |
118118
|Origin type| Select `Custom`.|
119-
|Origin host name| Enter `<tenant-name>.b2clogin.com`. Replace `<tenant-name>` with the [name of your Azure AD B2C tenant](tenant-management.md#get-your-tenant-name).|
119+
|Origin host name| Enter `<tenant-name>.b2clogin.com`. Replace `<tenant-name>` with the [name of your Azure AD B2C tenant](tenant-management.md#get-your-tenant-name) such as `contoso.b2clogin.com`.|
120120

121121
Leave the **Caching** and **WAF policy** empty.
122122

123123
124124
1. Once the Azure Front Door resource is created, select **Overview**, and copy the **Endpoint hostname**. It looks something like `b2cazurefrontdoor-ab123e.z01.azurefd.net`.
125125

126+
1. Make sure the **Host name** and **Origin host header** of your origin have the same value:
127+
1. Under **Settings**, select **Origin groups**.
128+
1. Select your origin group from the list, such as **default-origin-group**.
129+
1. On the right pane, select your **Origin host name** such as `contoso.b2clogin.com`.
130+
1. On the **Update origin** pane, update the **Host name** and **Origin host header** to have the same value.
131+
132+
:::image type="content" source="./media/custom-domain/azure-front-door-custom-domain-origins.png" alt-text="Screenshot of how to update custom domain origins.":::
133+
126134

127135
## Step 3. Set up your custom domain on Azure Front Door
128136

108 KB
Loading

articles/active-directory-b2c/self-asserted-technical-profile.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,9 @@ The validation technical profile can be any technical profile in the policy, suc
192192

193193
You can also call a REST API technical profile with your business logic, overwrite input claims, or enrich user data by further integrating with corporate line-of-business application. For more information, see [Validation technical profile](validation-technical-profile.md)
194194

195+
> [!NOTE]
196+
> A validation technical profile is only triggered when there's an input from the user. You can't create an _empty_ self-asserted technical profile to call a validation technical profile just to take advantage of the **ContinueOnError** attribute of a **ValidationTechnicalProfile** element. You can only call a validation technical profile from a self-asserted technical profile that requests an input from the user, or from an orchestration step in a user journey.
197+
195198
## Metadata
196199

197200
| Attribute | Required | Description |

articles/active-directory-b2c/threat-management.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The smart lockout feature uses many factors to determine when an account should
5555
- Passwords such as 12456! and 1234567! (or newAccount1234 and newaccount1234) are so similar that the algorithm interprets them as human error and counts them as a single try.
5656
- Larger variations in pattern, such as 12456! and ABCD2!, are counted as separate tries.
5757

58-
When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as [https://passwordsgenerator.net/](https://passwordsgenerator.net/).
58+
When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as `https://passwordsgenerator.net/`.
5959

6060
When the smart lockout threshold is reached, you'll see the following message while the account is locked: **Your account is temporarily locked to prevent unauthorized use. Try again later**. The error messages can be [localized](localization-string-ids.md#sign-up-or-sign-in-error-messages).
6161

@@ -69,4 +69,3 @@ To obtain information about locked-out accounts, you can check the Active Direct
6969
![Section of Azure AD sign-in report showing locked-out account](./media/threat-management/portal-01-locked-account.png)
7070

7171
To learn about viewing the sign-in activity report in Azure Active Directory, see [Sign-in activity report error codes](../active-directory/reports-monitoring/concept-sign-ins.md).
72-

articles/active-directory-domain-services/policy-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Built-in policy definitions for Azure Active Directory Domain Services
33
description: Lists Azure Policy built-in policy definitions for Azure Active Directory Domain Services. These built-in policy definitions provide common approaches to managing your Azure resources.
4-
ms.date: 07/20/2022
4+
ms.date: 07/26/2022
55
ms.service: active-directory
66
ms.subservice: domain-services
77
author: justinha

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-enable-tenant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To enable Permissions Management in your organization:
3737
## How to enable Permissions Management on your Azure AD tenant
3838

3939
1. In your browser:
40-
1. Go to [Entra services](https://entra.microsoft.com) and use your credentials to sign in to [Azure Active Directory](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview).
40+
1. Go to [Entra services](https://entra.microsoft.com) and use your credentials to sign in to [Azure Active Directory](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview).
4141
1. If you aren't already authenticated, sign in as a global administrator user.
4242
1. If needed, activate the global administrator role in your Azure AD tenant.
4343
1. In the Azure AD portal, select **Permissions Management**, and then select the link to purchase a license or begin a trial.

0 commit comments

Comments
 (0)