Currently there is no way to limit connection attempts to only your roles. It's only a "normal" firewall which, when open for "other Windows Services" will open the 1433 port to all Azure services. No way to distinguish by role.
About the protection - I guess the only protection is the default SQL Server Authentication. I cannot say though if there is some auto blocking mechanism for too many wrong password attempts.
Something else - when you create a server, you have a unique server name, which is unique to your account and not other. So in order for the "hostile role" to begin attempting connect to your server, it must first discover your server name. Then your administrator user (which is something you create) or a valid login.
发布评论
评论（1）
目前无法将连接尝试限制为仅限您的角色。它只是一个“普通”防火墙，当为“其他 Windows 服务”打开时，它将向所有 Azure 服务打开 1433 端口。无法按角色区分。
关于保护 - 我猜唯一的保护是默认的 SQL Server 身份验证。但我不能说是否有某种自动阻止机制来阻止过多的错误密码尝试。
其他 - 当您创建服务器时，您有一个唯一的服务器名称，该名称对于您的帐户来说是唯一的，而不是其他帐户。因此，为了让“敌对角色”开始尝试连接到您的服务器，它必须首先发现您的服务器名称。然后是您的管理员用户（您创建的用户）或有效的登录名。
Currently there is no way to limit connection attempts to only your roles. It's only a "normal" firewall which, when open for "other Windows Services" will open the 1433 port to all Azure services. No way to distinguish by role.
About the protection - I guess the only protection is the default SQL Server Authentication. I cannot say though if there is some auto blocking mechanism for too many wrong password attempts.
Something else - when you create a server, you have a unique server name, which is unique to your account and not other. So in order for the "hostile role" to begin attempting connect to your server, it must first discover your server name. Then your administrator user (which is something you create) or a valid login.