Restoring Your Azure SQL Managed Instance: Troubleshooting Common Errors

Have you encountered issues while restoring a database in your Azure SQL Managed Instance from Azure Blob Storage? Don’t worry, this guide will help you identify and fix common problems.

Facing Error 86: Incorrect Network Credentials

This error message indicates that the credentials used to access the blob storage are invalid. Here’s how to troubleshoot:

Verify Managed Identity Permissions: Regardless of your chosen identity type, ensure your SQL managed instance has the required permissions. It needs both “Storage Contributor” and “Storage Blob Data Contributor” roles assigned to its managed identity.
Check Existing Credentials: Use the query `select from sys.credentials` to verify existing credentials within your system.

Encountering Error 12007: Private Endpoint Issues

This error suggests a problem with your storage account’s private endpoint configuration. Here’s what could be causing it:

Disabled Public Network Access: If public network access is disabled for your storage account and you rely solely on a private endpoint, connectivity issues might arise.
Incorrect Private Endpoint Setup: Ensure the private endpoint for blob storage was created using the correct private DNS zone, which should be `privatelink.blob.core.windows.net`.

Validating Your Private Endpoint DNS Configuration

Follow these steps to check your private endpoint’s DNS configuration:

1. Navigate to your Azure Storage account.

2. Go to the “Network” section and then select “Private Endpoint.”

3. Click on the specific private endpoint you’re using.

4. Under “Settings”, find the “DNS configuration” option.

By following these steps and addressing the identified issues, you should be able to successfully restore your Azure SQL Managed Instance database from Azure Blob Storage.

Sources: Techcommunity.microsoft.com, Wikipedia, Internet Archive, 3D Printing Pros, Undercode Ai & Community
Image Source: Undercode AI DI v2, OpenAI