System Requirements for Azure SQL Managed Instance

Verify that your environment meets the system requirements for Azure SQL Managed Instance.

Azure Cloud

Verify that the following ports are open on the computer that has access to the Azure cloud:
- 443 to management.azure.com
- 1433 to *.database.windows.net
  
  Note
  
  Depending on your Azure environment, you might need to open additional ports. For more information, see Granting access to Azure SQL Database and SQL Data Warehouse in the Microsoft documentation.
- 22, on the access node computer with Red Hat Enterprise Linux operating system.
Verify that the Azure setup is using public clouds only.

Note

Sovereign clouds, such as in Germany or China, are not supported. For more information, go to Azure Regions Decision Guide in the Microsoft documentation.

On-Premises Access Nodes

If the client accesses Azure through an access node, then the user that runs the Commvault services must have the access node settings configured through Internet Explorer. If the Commvault services run under a local system account, then perform the following steps to set the access node settings:
1. To open a command window with the local system account, run the following command:
```
 
psexec.exe -i -s -d cmd.exe 
```
2. To confirm the user account, run the following command:
```
 
whoami.exe
```
3. To set the proxy server, run the following command:
```
 
iexplore.exe 
```
For restoring an on-premises backup to the Azure cloud:
- Install SQL Server on the access node.
  
  The operating system of the access node can be either Windows or Red Hat Enterprise Linux.
- Verify that the SQL server on the proxy client has the most recent SQL version so that the proxy server is in sync with the Azure instance.
  
  Note
  
  Azure always has the most recent SQL version.

SQL Server Authentication

You can use the following types of user accounts for data protection.

Azure Managed Instance Admin account: Managed instance administrator of the Azure SQL Managed instance.
Microsoft Entra Admin: Administrator account to centrally manage identity and access for your Azure SQL Managed instance.

Database user: Database level account that is used to configure minimal permissions for data protection operations. This authentication type will require the following minimum permissions:

Server-Level Roles	Database-Level Roles
dbcreator This role is required because the restore operation needs to create the database if it does not exist.	Login account and/or user account on the master database. A login account is recommended especially when managing multiple databases on the instance; the password is associated with the login account instead of with individual databases. A user account on the master database requires VIEW ANY DEFINITION permission. This is required to allow the gathering of metadata from sys.master_files and is only needed if you are not configuring a dbcreator server role for restore purposes. The user account at the databases level associated with the login account must have the following roles: db_backupoperator on the database that is being backed up db_datareader on the database that is being backed up

Server-Level Roles

Database-Level Roles

dbcreator

This role is required because the restore operation needs to create the database if it does not exist.

Login account and/or user account on the master database.

A login account is recommended especially when managing multiple databases on the instance; the password is associated with the login account instead of with individual databases.

A user account on the master database requires VIEW ANY DEFINITION permission. This is required to allow the gathering of metadata from sys.master_files and is only needed if you are not configuring a dbcreator server role for restore purposes.

The user account at the databases level associated with the login account must have the following roles:

db_backupoperator on the database that is being backed up
db_datareader on the database that is being backed up

Supported TLS Version

The software supports database protection operations on TLS version 1.2.