Skip to content

Commit 3a063c5

Browse files
authored
Merge pull request #180863 from MicrosoftDocs/master
11/23 AM Publish
2 parents 01b6784 + f224d95 commit 3a063c5

File tree

35 files changed

+136
-85
lines changed

35 files changed

+136
-85
lines changed

articles/active-directory-b2c/conditional-access-identity-protection-overview.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: overview
9-
ms.date: 05/28/2021
9+
ms.date: 11/23/2021
1010

1111
ms.author: kengaderdus
1212
author: kengaderdus
@@ -43,7 +43,7 @@ Identity Protection and Conditional Access in Azure AD B2C generally work the sa
4343

4444
- Identity Protection and Conditional Access aren't supported for ROPC server-to-server flows in Azure AD B2C tenants.
4545

46-
- In Azure AD B2C tenants, Identity Protection risk detections are available for local B2C accounts only, and not for social identities like Google or Facebook.
46+
- In Azure AD B2C tenants, Identity Protection risk detections are available for both local and social identities, such as Google or Facebook. For social identities, Conditional Access must be activated. Detection is limited because the social account credentials are managed by the external identity provider.
4747

4848
- In Azure AD B2C tenants, a subset of the Identity Protection risk detections is available. See [Investigate risk with Identity Protection](identity-protection-investigate-risk.md), and [Add Conditional Access to user flows](conditional-access-user-flow.md).
4949

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

Lines changed: 5 additions & 1 deletion
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: 09/15/2021
12+
ms.date: 11/23/2021
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
ms.custom: "b2c-support"
@@ -28,6 +28,10 @@ This article describes how to enable custom domains in your redirect URLs for Az
2828

2929
You can enable custom domains for Azure AD B2C by using [Azure Front Door](https://azure.microsoft.com/services/frontdoor/). Azure Front Door is a global entry point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications. You can render Azure AD B2C content behind Azure Front Door, and then configure an option in Azure Front Door to deliver the content via a custom domain in your application's URL.
3030

31+
Watch this video to learn about Azure AD B2C custom domain.
32+
33+
>[!Video https://www.youtube.com/embed/mVNB59VK-DQ]
34+
3135
The following diagram illustrates Azure Front Door integration:
3236

3337
1. From an application, a user selects the sign-in button, which takes them to the Azure AD B2C sign-in page. This page specifies a custom domain name.

articles/active-directory/devices/hybrid-azuread-join-federated-domains.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Hybrid Azure AD join requires devices to have access to the following Microsoft
8282
- `https://autologon.microsoftazuread-sso.com` (If you use or plan to use seamless SSO)
8383

8484
> [!WARNING]
85-
> If your organization uses proxy servers that intercept SSL traffic for scenarios like data loss prevention or Azure AD tenant restrictions, ensure that traffic to 'https://device.login.microsoftonline.com' is excluded from TLS break-and-inspect. Failure to exclude 'https://device.login.microsoftonline.com' may cause interference with client certificate authentication, causing issues with device registration and device-based Conditional Access.
85+
> If your organization uses proxy servers that intercept SSL traffic for scenarios like data loss prevention or Azure AD tenant restrictions, ensure that traffic to these URLs are excluded from TLS break-and-inspect. Failure to exclude these URLs may cause interference with client certificate authentication, cause issues with device registration, and device-based Conditional Access.
8686
8787
Beginning with Windows 10 1803, if the instantaneous hybrid Azure AD join for a federated environment by using AD FS fails, we rely on Azure AD Connect to sync the computer object in Azure AD that's subsequently used to complete the device registration for hybrid Azure AD join. Verify that Azure AD Connect has synced the computer objects of the devices you want to be hybrid Azure AD joined to Azure AD. If the computer objects belong to specific organizational units (OUs), you must also configure the OUs to sync in Azure AD Connect. To learn more about how to sync computer objects by using Azure AD Connect, see [Configure filtering by using Azure AD Connect](../hybrid/how-to-connect-sync-configure-filtering.md#organizational-unitbased-filtering).
8888

articles/active-directory/privileged-identity-management/pim-create-azure-ad-roles-and-resource-roles-review.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The need for access to privileged Azure resource and Azure AD roles by employees
3939

4040
:::image type="content" source="./media/pim-create-azure-ad-roles-and-resource-roles-review/identity-governance.png" alt-text="Select Identity Governance in Azure Portal screenshot." lightbox="./media/pim-create-azure-ad-roles-and-resource-roles-review/identity-governance.png":::
4141

42-
4. For **Azure AD roles**, select **Azure AD roles** again under **Manage**. For **Azure resources**, select the resource you want to manage, such as a subscription.
42+
4. For **Azure AD roles**, select **Azure AD roles** again under **Manage**. For **Azure resources**, select the subscription you want to manage.
4343

4444

4545
5. Under Manage, select **Access reviews**, and then select **New** to create a new access review.

articles/active-directory/saas-apps/cisco-webex-provisioning-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Before configuring Cisco Webex for automatic user provisioning with Azure AD, yo
5353

5454
4. In the search box, type **Cisco Webex**, select **Cisco Webex** from result panel then click **Add** button to add the application.
5555

56-
![Cisco Webex in the results list](common/search-new-app.png)
56+
![Cisco Webex in the results list](media/cisco-webex-provisioning-tutorial/search-cisco-app.png)
5757

5858
## Assigning users to Cisco Webex
5959

14.8 KB
Loading

articles/active-directory/verifiable-credentials/get-started-request-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ Authorization: Bearer <token>
231231

232232
For the complete code, see one of the following code samples:
233233

234-
- [C#](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/IssuerController.cs)
234+
- [C#](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs)
235235
- [Node.js](https://github.com/Azure-Samples/active-directory-verifiable-credentials-node/blob/main/1-node-api-idtokenhint/issuer.js)
236236

237237
## Presentation request example
@@ -317,7 +317,7 @@ try
317317
}
318318
```
319319

320-
For the complete code, see the [issuance](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/IssuerController.cs) and [presentation](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/VerifierController.cs) code on the GitHub repo.
320+
For the complete code, see the [issuance](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs) and [presentation](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs) code on the GitHub repo.
321321
322322
# [Node.js](#tab/nodejs)
323323

articles/aks/rdp.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,16 @@ This article shows you how to create an RDP connection with an AKS node using th
1818

1919
## Before you begin
2020

21-
This article assumes that you have an existing AKS cluster with a Windows Server node. If you need an AKS cluster, see the article on [creating an AKS cluster with a Windows container using the Azure CLI][aks-windows-cli]. You need the Windows administrator username and password for the Windows Server node you want to troubleshoot. If you don't know them, you can reset them by following [Reset Remote Desktop Services or its administrator password in a Windows VM
22-
](/troubleshoot/azure/virtual-machines/reset-rdp). You also need an RDP client such as [Microsoft Remote Desktop][rdp-mac].
21+
This article assumes that you have an existing AKS cluster with a Windows Server node. If you need an AKS cluster, see the article on [creating an AKS cluster with a Windows container using the Azure CLI][aks-windows-cli]. You need the Windows administrator username and password for the Windows Server node you want to troubleshoot. You also need an RDP client such as [Microsoft Remote Desktop][rdp-mac].
22+
23+
If you need to reset the password you can use `az aks update` to change the password.
24+
25+
```azurecli-interactive
26+
az aks update -g myResourceGroup -n myAKSCluster --windows-admin-password $WINDOWS_ADMIN_PASSWORD
27+
```
28+
29+
If you need to reset both the username and password, see [Reset Remote Desktop Services or its administrator password in a Windows VM
30+
](/troubleshoot/azure/virtual-machines/reset-rdp).
2331

2432
You also need the Azure CLI version 2.0.61 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
2533

articles/azure-cache-for-redis/cache-how-to-scale.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,10 @@ Choose a pricing tier on the right and then choose **Select**.
4545

4646
:::image type="content" source="media/cache-how-to-scale/select-a-tier.png" alt-text="Azure Cache for Redis tiers":::
4747

48+
> [!NOTE]
49+
> Scaling is currently not avaialble with Enterprise Tier.
50+
>
51+
4852
You can scale to a different pricing tier with the following restrictions:
4953

5054
- You can't scale from a higher pricing tier to a lower pricing tier.

articles/azure-cache-for-redis/cache-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ The Enterprise tiers rely on Redis Enterprise, a commercial variant of Redis fro
9494
> separately from cache instances themselves. For more information, see [Load Balancer pricing](https://azure.microsoft.com/pricing/details/load-balancer/).
9595
> If an Enterprise cache is configured for multiple Availability Zones, data
9696
> transfer will be billed at the [standard network bandwidth rates](https://azure.microsoft.com/pricing/details/bandwidth/)
97-
> starting from July 1, 2021.
97+
> starting from July 1, 2022.
9898
>
9999
> In addition, data persistence adds Managed Disks. The use of these resources will be free during
100100
> the public preview of Enterprise data persistence. This may change when the feature becomes
@@ -111,4 +111,4 @@ The Enterprise tiers rely on Redis Enterprise, a commercial variant of Redis fro
111111
* [Use Azure Cache for Redis in .NET Framework](cache-dotnet-how-to-use-azure-redis-cache.md)
112112
* [Use Azure Cache for Redis in Node.js](cache-nodejs-get-started.md)
113113
* [Use Azure Cache for Redis in Java](cache-java-get-started.md)
114-
* [Use Azure Cache for Redis in Python](cache-python-get-started.md)
114+
* [Use Azure Cache for Redis in Python](cache-python-get-started.md)

0 commit comments

Comments
 (0)