Apply Microsoft Learn documentation standards

- Use proper NOTE alert syntax instead of heading
- Apply sentence case for 'Customer responsibility'
- Improve grammar and use active voice
- Use full product name 'Azure role-based access control (RBAC)'
- Remove unnecessary punctuation in list items
- Update ms.date to 11/24/2025

Fixes MicrosoftDocs/sql-docs-pr#35810

Author: VanMSFT

azure-sql/database/auditing-microsoft-support-operations.md

@@ -5,7 +5,7 @@ description: How to use Auditing to audit Microsoft support operations.
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: mathoma, vanto
-ms.date: 09/18/2025
+ms.date: 11/24/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: conceptual
@@ -37,15 +37,13 @@ AzureDiagnostics
 
 You have the option of choosing a different storage destination for this auditing log, or use the same auditing configuration for your server.
 
-### Note
-
-DevOps Audit Logs stored in **Microsoft Azure Storage** may contain sensitive operational details. If accessed by a malicious actor within the customer environment, could gain insights into system operations, which may lead to unauthorized access or data breaches. 
-
-**Customer Responsibility:**  
-Secure these logs by:
-- Restricting access to authorized personnel only.
-- Applying strong Azure RBAC and network controls.
-- Monitoring and auditing storage access regularly.
+> [!NOTE]
+> DevOps audit logs stored in Azure Storage may contain sensitive operational details. If a malicious actor within your environment accesses these logs, they could gain insights into system operations, which may lead to unauthorized access or data breaches.
+>
+> **Customer responsibility -** Secure these logs by:
+> - Restricting access to authorized personnel only
+> - Applying strong Azure role-based access control (RBAC) and network controls
+> - Monitoring and auditing storage access regularly
 
 ## Related content