Skip to content

Commit 3c92512

Browse files
committed
revise warning
1 parent 526e8db commit 3c92512

File tree

2 files changed

+5
-6
lines changed

2 files changed

+5
-6
lines changed

articles/expressroute/expressroute-troubleshooting-arp-resource-manager.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,31 +3,30 @@ title: 'Azure ExpressRoute: ARP tables - Troubleshooting'
33
description: This page provides instructions on getting the Address Resolution Protocol (ARP) tables for an ExpressRoute circuit
44
services: expressroute
55
author: duongau
6-
76
ms.service: expressroute
87
ms.topic: troubleshooting
9-
ms.date: 12/15/2020
8+
ms.date: 01/05/2022
109
ms.author: duau
1110
ms.custom: seodec18, devx-track-azurepowershell
1211

1312
---
1413
# Getting ARP tables in the Resource Manager deployment model
14+
1515
> [!div class="op_single_selector"]
1616
> * [PowerShell - Resource Manager](expressroute-troubleshooting-arp-resource-manager.md)
1717
> * [PowerShell - Classic](expressroute-troubleshooting-arp-classic.md)
1818
>
19-
>
2019
2120
This article walks you through the steps to learn the ARP tables for your ExpressRoute circuit.
2221

2322
> [!IMPORTANT]
2423
> This document is intended to help you diagnose and fix simple issues. It is not intended to be a replacement for Microsoft support. You must open a support ticket with [Microsoft support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade) if you are unable to solve the problem using the guidance described below.
2524
>
26-
>
2725
2826
[!INCLUDE [updated-for-az](../../includes/hybrid-az-ps.md)]
2927

3028
## Address Resolution Protocol (ARP) and ARP tables
29+
3130
Address Resolution Protocol (ARP) is a layer 2 protocol defined in [RFC 826](https://tools.ietf.org/html/rfc826). ARP is used to map the Ethernet address (MAC address) with an ip address.
3231

3332
The ARP table provides the following information for both the primary and secondary interfaces for each peering types:

articles/frontdoor/front-door-custom-domain-https.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,12 +157,12 @@ Azure Front Door can now access this key vault and the certificates it contains.
157157
- The available secret versions.
158158
159159
> [!NOTE]
160-
> In order for the certificate to be automatically rotated to the latest version when a newer version of the certificate is available in your Key Vault, please set the secret version to 'Latest'. If a specific version is selected, you have to re-select the new version manually for certificate rotation. It takes up to 72 hours for the new version of the certificate/secret to be deployed.
160+
> In order for the certificate to be automatically rotated to the latest version when a newer version of the certificate is available in your Key Vault, set the secret version to 'Latest'. If a specific version is selected, you have to re-select the new version manually for certificate rotation. It takes up to 72 hours for the new version of the certificate/secret to be deployed.
161161
>
162162
> :::image type="content" source="./media/front-door-custom-domain-https/certificate-version.png" alt-text="Screenshot of selecting secret version on update custom domain page.":::
163163
164164
> [!WARNING]
165-
> This is a portal only warning. Besides configuring Service Principal to have Get permission on the Key Vault, for the user to be able to see the certificate in the portal dropdown, the user account itself need to have LIST and GET permission on the Key Vault. If the user doesn't have these permissions, they will see inaccessible error message on portal. However, the inccessible error message doesn't have impact on certificate autorotation or any HTTPS function. No action is required for this error message if you don't intend to make changes to the certificate or version. But if you want to change anything in this page, please follow [Provide pemrission to Key Vault](https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide?tabs=azure-cli) to add your account to the LIST and GET permission on the Key Vault.
165+
> This is an Azure portal only warning. You need to configure your service principal to have a GET permission on the Key Vault. In order for a user to see the certificate in the portal drop-down, the user account must have LIST and GET permissions on the Key Vault. If a user doesn't have these permissions, they'll see an inaccessible error message in portal. An inaccessible error message doesn't have any impact on certificate auto-rotation or any HTTPS function. No actions are required for this error message if you don't intend to make changes to the certificate or the version. If you want to change the information on this page, see [provide permission to Key Vault](../key-vault/general/rbac-guide.md?tabs=azure-cli) to add your account to the LIST and GET permission of the Key Vault.
166166
167167
168168
5. When you use your own certificate, domain validation isn't required. Continue to [Wait for propagation](#wait-for-propagation).

0 commit comments

Comments
 (0)