Hello @Hatem MAHBOULI (EXT) For an elaborated response to your request. When setting up active geo-replication between two different tenants in Azure SQL Database, there are several security measures and configurations to consider preventing unauthorized access:
- Authentication and Access Control: Azure SQL Database supports SQL authentication and Microsoft Entra ID (formerly Azure Active Directory) authentication1. It’s important to manage databases and servers within Azure using your portal user account’s role assignments.
- Contained Users: Unlike traditional users, which must be mapped to logins in the master database, a contained user is managed completely by the database itself2. This means users can continue to connect to the new primary database or the database recovered using geo-restore without any additional configuration.
- Firewall Rules: Azure SQL Database provides a firewall that enables you to create rules limiting connectivity by IP address1. You can set up server-level firewall rules accessible from the Azure portal and database-level firewall rules accessible from SSMS.
- Data Encryption: Azure SQL Database supports Transport Layer Security for data encryption when data is moving to the networks3. It also supports Transparent Data Encryption for encryption at rest.
- Auditing and Threat Detection: Azure SQL Database auditing tracks database events and writes them to an audit log in your Azure Storage account3. Threat detection detects anomalous database activities indicating potential security threats to the database.
- Managed Service Identities: The best way to lock down your SQL Database is with AAD Integration, and Managed Service Identities4. Azure will provision an AAD identity for your application, and only code running in that application will be able to generate an Access Token for that Identity4.
Remember, it’s crucial to grant users the least privileges necessary and regularly review and update your security configurations. For more detailed information, you can refer to the Azure SQL Database Security Overview and the Azure Database Security Checklist. If this information provided here helps solve your issue, please tag this as answered, so it helps further community readers, who may have similar questions.