Update docs with new ms.date and schema change notes

Updated the ms.date metadata in two documentation files to 11/27/2025. Removed example Kusto queries and explanatory text from advanced-hunting-schema-changes.md regarding Boolean field value changes, streamlining the November 2025 schema change notes.

Author: poliveria

defender-xdr/advanced-hunting-devicetvmsecureconfigurationassessment-table.md

@@ -21,7 +21,7 @@ appliesto:
     - Microsoft Defender XDR
     - Microsoft Sentinel in the Microsoft Defender portal
 ms.topic: reference
-ms.date: 03/28/2025
+ms.date: 11/27/2025
 ---
 
 # DeviceTvmSecureConfigurationAssessment

defender-xdr/advanced-hunting-schema-changes.md

@@ -21,7 +21,7 @@ appliesto:
     - Microsoft Defender XDR
     - Microsoft Sentinel in the Microsoft Defender portal
 ms.topic: reference
-ms.date: 11/04/2025
+ms.date: 11/27/2025
 ---
 
 # Advanced hunting schema - Naming changes
@@ -40,21 +40,6 @@ Naming changes are automatically applied to queries that are saved in Microsoft
 ## November 2025
 - The Boolean field values in advanced hunting results will change from numeric (`1` and `0`) to textual (`True` and `False`) on January 25, 2026. While your queries and custom detection rules won't be affected by this change, you might want to update your automated processes (for example, scripts, playbooks, or integrations) parsing these values.
 
-    For example:
-
-    **Current behavior**
-    ```kusto
-    DeviceEvents 
-    | where IsAdmin == 1 
-    ```
-
-    **Future behavior**
-    ```kusto
-    DeviceEvents 
-    | where IsAdmin == true 
-    ```
-
-    Both queries will remain valid. However, if your automation expects `IsAdmin=1` in the output, update it to accept `true` instead. 
 
 - The [`AADSignInEventsBeta`](advanced-hunting-aadsignineventsbeta-table.md) and  [`AADSpnSignInEventsBeta`](advanced-hunting-aadspnsignineventsbeta-table.md) tables are being replaced by [`EntraIdSignInEvents`](advanced-hunting-entraidsigninevents-table.md) and [`EntraIdSpnSignInEvents`](advanced-hunting-entraidspnsigninevents-table.md), respectively. These changes are being made to remove the former tables' preview status and to align them with the existing product branding.