Improve Acrolinx score: use active voice, spell out contractions, follow Microsoft style guide

Author: Edewe Bolton

.github/copilot-instructions.md

@@ -0,0 +1,57 @@
+# Copilot Instructions for Microsoft Learn
+
+These instructions define a unified style and process standard for authoring and maintaining learn.microsoft.com documentation with GitHub Copilot or other AI assistance.
+
+## Learn-wide Instructions
+
+Below are instructions that apply to all Microsoft Learn documentation authored with AI assistance. Learn product team will update this periodically as needed. Each repository SHOULD NOT update this to avoid being overwritten, but update the repository-specific instructions below as needed.
+
+### AI Usage & Disclosure
+All Markdown content created or substantially modified with AI assistance must include an `ai-usage` front matter entry:
+- `ai-usage: ai-generated` – AI produced the initial draft with minimal human authorship
+- `ai-usage: ai-assisted` – Human-directed, reviewed, and edited with AI support
+- Omit only for purely human-authored legacy content
+
+If missing, **add it**. However, do not add or update the ai-usage tag if the changes proposed are confined solely to:
+- Links (link text and/or URLs)
+- Single words or short phrases, such as entries in table cells
+- Less than 5% of the article's word count
+
+### Writing Style
+
+Follow [Microsoft Writing Style Guide](https://learn.microsoft.com/style-guide/welcome/) with these specifics:
+
+#### Voice and Tone
+
+- Active voice, second person addressing reader directly
+- Conversational tone with contractions
+- Present tense for instructions/descriptions
+- Imperative mood for instructions ("Call the method" not "You should call the method")
+- Use "might" instead of "may" for possibility
+- Avoid "we"/"our" referring to documentation authors
+
+#### Structure and Format
+
+- Sentence case headings (no gerunds in titles)
+- Be concise, break up long sentences
+- Oxford comma in lists
+- Number all ordered list items as "1." (not sequential numbering like "1.", "2.", "3.", etc.)
+- Complete sentences with proper punctuation in all list items
+- Avoid "etc." or "and so on" - provide complete lists or use "for example"
+- No consecutive headings without content between them
+
+#### Formatting Conventions
+
+- **Bold** for UI elements
+- `Code style` for file names, folders, custom types, non-localizable text
+- Raw URLs in angle brackets
+- Use relative links for files in this repo
+- Remove `https://learn.microsoft.com/en-us` from learn.microsoft.com links
+
+## Repository-Specific Instructions
+
+Below are instructions specific to this repository. These may be updated by repository maintainers as needed.
+
+<!--- Add additional repository level instructions below. Do NOT update this line or above. --->
+
+

.openpublishing.publish.config.json

@@ -85,6 +85,12 @@
       "url": "https://github.com/MicrosoftDocs/azure-docs-pr",
       "branch": "main",
       "branch_mapping": {}
+    },
+    {
+        "path_to_root": "azure-policy-autogen-docs",
+        "url": "https://github.com/MicrosoftDocs/azure-policy-autogen-docs",
+        "branch": "main",
+        "branch_mapping": {}
     }
   ],
   "branch_target_mapping": {},

.openpublishing.redirection.json

@@ -1,5 +1,125 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/container-instances/quickstart-docker-cli.md",
+      "redirect_url": "/previous-versions/azure/container-instances/quickstart-docker-cli",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/service-fabric/service-fabric-diagnostics-event-analysis-appinsights.md",
+      "redirect_url": "/previous-versions/azure/service-fabric/service-fabric-diagnostics-event-analysis-appinsights",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/service-fabric/service-fabric-tutorial-monitoring-aspnet.md",
+      "redirect_url": "/previous-versions/azure/service-fabric/service-fabric-tutorial-monitoring-aspnet",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machine-scale-sets/whats-new.md",
+      "redirect_url": "/previous-versions/azure/virtual-machine-scale-sets/whats-new",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/mainframe-white-papers.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/mainframe-white-papers",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/overview.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-impact-reporting/report-vm-impact.md",
+      "redirect_url": "/azure/azure-impact-reporting/report-impact",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/partner-workloads.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/partner-workloads",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/concepts/mainframe-compute-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/concepts/mainframe-compute-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/concepts/mainframe-storage-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/concepts/mainframe-storage-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/ibm/demo.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/ibm/demo",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/ibm/deploy-ibm-db2-purescale-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/ibm/deploy-ibm-db2-purescale-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/ibm/get-started.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/ibm/get-started",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/ibm/ibm-db2-purescale-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/ibm/ibm-db2-purescale-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/ibm/install-ibm-z-environment.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/ibm/install-ibm-z-environment",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/microfocus/demo.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/microfocus/demo",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/microfocus/deploy-micro-focus-enterprise-server.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/microfocus/deploy-micro-focus-enterprise-server",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/microfocus/get-started.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/microfocus/get-started",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/microfocus/run-enterprise-server-container.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/microfocus/run-enterprise-server-container",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/microfocus/set-up-micro-focus-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/microfocus/set-up-micro-focus-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/tmaxsoft/get-started.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/tmaxsoft/get-started",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/workloads/mainframe-rehosting/tmaxsoft/install-openframe-azure.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/workloads/mainframe-rehosting/tmaxsoft/install-openframe-azure",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/extensions/oms-linux.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/extensions/oms-linux",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/virtual-machines/extensions/oms-windows.md",
+      "redirect_url": "/previous-versions/azure/virtual-machines/extensions/oms-windows",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/virtual-machines/sizes/gpu-accelerated/nc-series.md",
       "redirect_url": "/previous-versions/azure/virtual-machines/sizes/gpu-accelerated/nc-series",

articles/azure-impact-reporting/azure-monitor-connector.md

@@ -1,27 +1,30 @@
 ---
-title: Azure Impact Reporting - Azure Monitor Alert Connector #Required; page title is displayed in search results. Include the brand.
-description: Seamlessly report impact through Azure Monitor alerts. #Required; article description that is displayed in search results. 
-author: rolandnyamo #Required; your GitHub user alias, with correct capitalization.
-ms.author: ronyamo #Required; microsoft alias of author; optional team alias.
-ms.service: azure #Required; use either service or product per approved list. 
-ms.topic: overview #Required; leave this attribute/value as-is.
-ms.date: 06/19/2024 #Required; mm/dd/yyyy format.
-ms.custom: template-overview #Required; leave this attribute/value as-is.
+title: 'Azure Impact Reporting: Azure Monitor Alert Connector'
+description: Learn how to seamlessly report impact through Azure Monitor alerts. 
+author: rolandnyamo
+ms.author: ronyamo
+ms.service: azure 
+ms.topic: overview
+ms.date: 09/17/2025
+ms.custom: template-overview
+# Customer intent: "As a systems administrator, I want to use the Impact Connector for Azure Monitor alerts so that I can efficiently report impact events and enhance change event correlation within my organization's AI operations workflows."
 ---
 
-# What is the Impact Connector for Azure Monitor Alerts? (Preview)
+# What is the impact connector for Azure Monitor alerts (preview)?
+
 > [!IMPORTANT]
-> Azure Impact Reporting is currently in Preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+> Azure Impact Reporting is currently in preview. For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
+When you use the impact connector for Azure Monitor alerts, you can seamlessly report the impact from an alert into Microsoft AI operations for change event correlation.
 
-The impact Connector for Azure Monitor alerts enables you to seamlessly report impact from an alert into Microsoft AIOps for change event correlation.
+## How connectors work
 
-## How Connectors work
+[![Diagram that shows the architecture of impact connectors for Azure Monitor.](images/azure-monitor-connector.png)](images/azure-monitor-connector.png#lightbox)
 
-![Architecture diagram of impact connectors for azure monitor.](images/azure-monitor-connector.png)
+When you create a connector, it gets associated with a subscription. When alerts whose target resources reside in the specified subscription are fired, an impact report is created through Azure Impact Reporting and sent to Microsoft intelligence systems.
 
-When you create a connector, it gets associated with a subscription. When alerts whose target resources reside in the specified subscription get fired, an Impact report is created through Azure Impact Reporting and sent to Microsoft Intelligence Systems.
+## Related content
 
-## Next steps
-* [Create a Connector for Azure Monitor Alerts](create-azure-monitor-connector.md).
-* [Impact Reporting Connectors - Troubleshooting Guide](connectors-troubleshooting-guide.md).
-* [View Reported Impacts and Insights](view-impact-insights.md).
+* [Create a connector for Azure Monitor alerts](create-azure-monitor-connector.md)
+* [Impact Reporting connectors: Troubleshooting guide](connectors-troubleshooting-guide.md)
+* [View reported impacts and insights](view-impact-insights.md)

articles/azure-impact-reporting/connectors-faq.md

@@ -1,49 +1,53 @@
 ---
-title: Azure Impact Connectors for Azure Monitor - FAQ #Required; page title is displayed in search results. Include the brand.
-description: Frequently asked questions for Azure Monitor Connectors. #Required; article description that is displayed in search results. 
-author: rolandnyamo #Required; your GitHub user alias, with correct capitalization.
-ms.author: ronyamo #Required; microsoft alias of author; optional team alias.
-ms.topic: faq #Required; leave this attribute/value as-is.
-ms.service: azure #Required; use either service or product per approved list. 
-ms.date: 06/25/2024 #Required; mm/dd/yyyy format
-ms.custom: template-overview #Required; leave this attribute/value as-is.
+title: 'Azure Impact Reporting Connectors for Azure Monitor: FAQ'
+description: Frequently asked questions about Azure Monitor connectors. 
+author: rolandnyamo
+ms.author: ronyamo
+ms.topic: faq
+ms.service: azure 
+ms.date: 06/25/2024
+ms.custom: template-overview
+# Customer intent: As an Azure administrator, I want to troubleshoot and configure Azure Impact Reporting connectors so that I can ensure successful integration with Azure Monitor and manage permissions effectively.
 ---
 
-# Azure Impact Reporting Connectors for Azure Monitor FAQ (Preview)
+# Azure Impact Reporting connectors for Azure Monitor (preview) FAQ
+
 > [!IMPORTANT]
-> Azure Impact Reporting is currently in Preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+> Azure Impact Reporting is currently in preview. For legal terms that apply to Azure features that are in beta, in preview, or otherwise not yet released into general availability, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Here are answers to common questions about Azure Impact Reporting Connectors.
+Here are answers to common questions about Azure Impact Reporting connectors.
 
 ## How do I enable debug mode?
 
 * **Bash**: Uncomment the `set -x` at the beginning of the script.
-* **Powershell**: Change `Set-PSDebug -Trace 0 to Set-PSDebug -Trace 1` at the beginning
+* **PowerShell**: Change `Set-PSDebug -Trace 0` to `Set-PSDebug -Trace 1` at the beginning.
 
 ## What should I do if I encounter a permission error?
 
-Verify your Azure role and permissions. You may need the help of your Azure administrator to grant you the necessary permissions or roles as defined in the permissions section.
+Verify your Azure role and permissions. You might need the help of your Azure administrator to grant you the necessary permissions or roles as defined in the permissions section.
 
 ## How can I verify if the connector is successfully created?
+
 ### Option 1
+
 * **Bash**:
-    * Step 1: Run this command: 
-`az rest --method get --url https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.Impact/connectors?api-version=2024-05-01-preview`.
-    * Step 2: You should see a resource with the name `AzureMonitorConnector`.
-* **Powershell**:
-    * Step 1: Run this command: 
-`(Invoke-AzRestMethod -Method Get -Path subscriptions/<Subscription Id>/providers/Microsoft.Impact/connectors?api-version=2024-05-01-preview).Content`.
-    * Step 2: You should see a resource with the name `AzureMonitorConnector`.
+    * Run the command `az rest --method get --url https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.Impact/connectors?api-version=2024-05-01-preview`.
+    * You should see a resource with the name `AzureMonitorConnector`.
+* **PowerShell**:
+    * Run the command `(Invoke-AzRestMethod -Method Get -Path subscriptions/<Subscription Id>/providers/Microsoft.Impact/connectors?api-version=2024-05-01-preview).Content`.
+    * You should see a resource with the name `AzureMonitorConnector`.
 
 ### Option 2
-* Step 1: From the Azure portal, navigate to [Azure Resource Graph Explorer](https://portal.azure.com/#view/HubsExtension/ArgQueryBlade).
-* Step 2: Run this query: 
-```kql
-impactreportresources  | where name == "AzureMonitorConnector"  and type == "microsoft.impact/connectors"
-```
 
-## Next steps
+1. In the Azure portal, go to [Azure Resource Graph Explorer](https://portal.azure.com/#view/HubsExtension/ArgQueryBlade).
+
+1. Run this query:
+
+    ```kql
+    impactreportresources  | where name == "AzureMonitorConnector"  and type == "microsoft.impact/connectors"
+    ```
+
+## Related content
 
-* [File an impact report](report-vm-impact.md).
-<!-- Add Impact Connectors TSG -->
-<!-- - [File an impact report](report-vm-impact.md) -->
+* [File an impact report](report-impact.md)
+* [Create an impact connector for Azure Monitor alerts](create-azure-monitor-connector.md)