Merge pull request #36247 from WilliamDAssafMSFT/20260114-json-valid

20260114 json valid

Author: prmerger-automator[bot]

docs/t-sql/data-types/json-data-type.md

@@ -4,7 +4,7 @@ description: The native JSON data type provides advantages for storing JSON data
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest, jovanpop, umajay
-ms.date: 11/18/2025
+ms.date: 01/14/2026
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -102,6 +102,26 @@ SET d.modify('$.b', 'def')
 WHERE id = 1;
 ```
 
+## Valid data
+
+Input to the **json** data type must be a JSON object or a JSON array. Scalars, booleans, and `NULL` values are not supported. The JSON data type conforms to IETF RFC 4627 which allows only a JSON object or array. The **json** data type and all JSON functions only work with IETF RFC 4627 compliant JSON documents.
+
+The [ISJSON](../functions/isjson-transact-sql.md) function can be used to validate a string that contains JSON document conforms to IETF RFC 8259. An IETF RFC 8259 conformant JSON document contains only a JSON scalar value at top level. 
+
+For example:
+
+```sql
+DECLARE @true JSON = 'true'; -- invalid
+DECLARE @false JSON = 'false'; -- invalid
+DECLARE @number JSON = '1234.56'; -- invalid
+DECLARE @string JSON = '"contoso"'; -- invalid
+DECLARE @null JSON = 'null' -- invalid
+
+DECLARE @null JSON = NULL -- valid
+DECLARE @object JSON = '{}' -- valid
+DECLARE @array JSON = '[]' -- valid
+```
+
 ## Function support
 
 All JSON functions support the **json** data type with no code changes or usage difference necessary.

docs/t-sql/functions/isjson-transact-sql.md

@@ -62,7 +62,7 @@ If the *json_type_constraint* is specified then the function checks for the JSON
 |`OBJECT`|Tests for a valid JSON object|
 |`SCALAR`|Tests for a valid JSON scalar – number or string|
 
- The **json_type_constraint** value SCALAR can be used to test for IETF RFC 8259 conformant JSON document that contains only a JSON scalar value at top level. A JSON document that doesn't contain a JSON scalar value at top level conforms with IETF RFC 4627.
+ The `json_type_constraint` value SCALAR can be used to test for IETF RFC 8259 conformant JSON document that contains only a JSON scalar value at top level. A JSON document that doesn't contain a JSON scalar value at top level conforms with IETF RFC 4627.
 
 Does not return errors.