Skip to content

Commit d2ef1d0

Browse files
committed
Merge branch 'akv-misc' of https://github.com/msmbaldwin/azure-docs-pr into akv-misc
2 parents 58ff619 + 411acac commit d2ef1d0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/databox-online/azure-stack-edge-gpu-troubleshoot-activation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ The following table summarizes the errors related to device activation and the c
4848

4949
| Error message| Recommended resolution |
5050
|------------------------------------------------------|--------------------------------------|
51-
| If the diagnostic setting creation fails for your key vault, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | This is not a blocking error and the activation key will be generated. <br> You can manually [Create a diagnostic setting to store your audit logs](../key-vault/general/howto-logging.md#create-a-storage-account-for-your-logs). |
52-
| If the storage account creation fails, for example, because an account already exists for the name you specified, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | You can manually create a storage account and link it to the diagnostic setting on your key vault. This account is then used to store audit logs. <br> For more information, see [Create a storage account for your logs](../key-vault/general/howto-logging.md#create-a-storage-account-for-your-logs). |
51+
| If the diagnostic setting creation fails for your key vault, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | This is not a blocking error and the activation key will be generated. <br>You can manually [Create a diagnostic setting to store your audit logs](../key-vault/general/howto-logging.md). |
52+
| If the storage account creation fails, for example, because an account already exists for the name you specified, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | You can manually create a storage account and link it to the diagnostic setting on your key vault. This account is then used to store audit logs. <br> For more information, see [Create a storage account for your logs](../key-vault/general/howto-logging.md). |
5353
|If the system assigned managed identity for your Azure Stack Edge resource is deleted, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | You'll see an alert in the Security blade for your Azure Stack Edge resource. Select this alert to [Create a new managed identity through the Recover key vault blade](azure-stack-edge-gpu-activation-key-vault.md#recover-key-vault) |
5454
| If the managed identity doesn't have access to the key vault, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | You'll see an alert in the Security blade for your Azure Stack Edge resource. Select this alert to [Grant managed identity access to the key vault through the Recover key vault blade](azure-stack-edge-gpu-activation-key-vault.md#recover-key-vault). |
5555

@@ -59,7 +59,7 @@ The following table summarizes the errors related to device activation and the c
5959
|------------------------------------------------------|--------------------------------------|
6060
| If the key vault resource is moved across resource groups or subscriptions, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | The key vault resource move is treated the same way as key vault deletion. You can restore the key vault if the vault is in purge-protection duration. If the purge-protection duration has elapsed, then you'll need to create a new key vault. For more information on either of the above cases, see [Recover a key vault](azure-stack-edge-gpu-activation-key-vault.md#recover-key-vault). |
6161
| If the subscription you are using, is moved across tenants, you'll see this error. <!--<br> ![Key vault error 3](./media/azure-stack-edge-gpu-activation-key-vault/placeholder.png)--> | Reconfigure managed identity and create a new key vault. You can also move the key vault resource in which case only the managed identity will need to be reconfigured. In each of the above cases, see [Recover a key vault](azure-stack-edge-gpu-activation-key-vault.md#recover-key-vault). |
62-
| If the storage account resource that is used for audit logs, is moved across resource groups or subscriptions, you won't see an error. | You can [Create a new storage account and configure it to store the audit logs](../key-vault/general/howto-logging.md#create-a-storage-account-for-your-logs). |
62+
| If the storage account resource that is used for audit logs, is moved across resource groups or subscriptions, you won't see an error. | You can [Create a new storage account and configure it to store the audit logs](../key-vault/general/howto-logging.md). |
6363

6464
## Other errors
6565

0 commit comments

Comments
 (0)