Azure SQL Database General Limitations and Guidelines
This topic provides general limitations and guidelines for Azure SQL Database. For a complete understanding of quotas, resource management, and support, please see the additional resources at the end of this topic.
Windows Authentication is not supported. See Managing Databases and Logins in Azure SQL Database. However, Azure Active Directory Authentication is supported with certain limitations. See Connect to SQL Database with Azure Active Directory Authentication.
Microsoft Azure SQL Database supports tabular data stream (TDS) protocol client version 7.3 or later.
Only TCP/IP connections are allowed.
The SQL Server 2008 SQL Server browser is not supported because Microsoft Azure SQL Database does not have dynamic ports, only port 1433.
Microsoft Azure SQL Database does not support SQL Server Agent, however you can use Elastic jobs to run jobs across one to many databases. For more information about Elastic jobs, see Elastic jobs.
The default database collation used by Microsoft Azure SQL Database is SQL_LATIN1_GENERAL_CP1_CI_AS, where LATIN1_GENERAL is English (United States), CP1 is code page 1252, CI is case-insensitive, and AS is accent-sensitive. It is not possible to alter the collation for V12 databases. For more information about how to set the collation, see COLLATE (Transact-SQL).
Certain user names are not allowed for security reasons. You cannot use the following names:
Names for all new objects must comply with the SQL Server rules for identifiers. For more information, see Identifiers.
Additionally, login and user names cannot contain the \ character (Windows Authentication is not supported).
In addition to the general limitations outlined in this article, SQL Database has specific resource quotas and limitations based on your service tier. For an overview of service tiers, see SQL Database service tiers.
For other SQL Database limits, see Azure SQL Database Resource Limits.
For security related guidelines, see Azure SQL Database Security Guidelines and Limitations.
Another related area surrounds the compatibility that Azure SQL Database has with on-premises versions of SQL Server, such as SQL Server 2014 and SQL Server 2016. The latest V12 version of Azure SQL Database has made many improvements in this area. For more details, see What's new in SQL Database V12.
For information on driver availability and support for SQL Database, see Connection Libraries for SQL Database and SQL Server.