Merge pull request #19372 from MicrosoftDocs/stevestein-patch-1

SQL DB and MI UTF-8 support

Author: PRMerger7

docs/relational-databases/collations/collation-and-unicode-support.md

@@ -576,6 +576,8 @@ These collations are supported in [!INCLUDE[ssde_md](../../includes/ssde_md.md)]
 
 UTF-8 is available only to Windows collations that support supplementary characters, as introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]. The **nchar** and **nvarchar** data types allow UCS-2 or UTF-16 encoding only, and they remain unchanged.
 
+Azure SQL Database and Azure SQL Managed Instance also support UTF-8.
+
 ### <a name="storage_differences"></a> Storage differences between UTF-8 and UTF-16
 The Unicode Consortium allocates to each character a unique code point, which is a value in the range 000000–10FFFF. With [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], both UTF-8 and UTF-16 encodings are available to represent the full range:    
 -  With UTF-8 encoding, characters in the ASCII range (000000–00007F) require 1 byte, code points 000080–0007FF require 2 bytes, code points 000800–00FFFF require 3 bytes, and code points 0010000–0010FFFF require 4 bytes. 
@@ -650,4 +652,4 @@ For more information, see the following related content:
 [Contained Database Collations](../../relational-databases/databases/contained-database-collations.md)     
 [Choose a Language When Creating a Full-Text Index](../../relational-databases/search/choose-a-language-when-creating-a-full-text-index.md)     
 [sys.fn_helpcollations (Transact-SQL)](../../relational-databases/system-functions/sys-fn-helpcollations-transact-sql.md)       
-[Single-Byte and Multibyte Character Sets](/cpp/c-runtime-library/single-byte-and-multibyte-character-sets)
+[Single-Byte and Multibyte Character Sets](/cpp/c-runtime-library/single-byte-and-multibyte-character-sets)