Merge remote-tracking branch 'upstream/main' into delete-include-files

Author: msjasteppe

articles/ddos-protection/test-through-simulations.md

@@ -25,6 +25,7 @@ You can only simulate attacks using our approved testing partners:
 - [BreakingPoint Cloud](https://www.ixiacom.com/products/breakingpoint-cloud): a self-service traffic generator where your customers can generate traffic against DDoS Protection-enabled public endpoints for simulations. 
 - [Red Button](https://www.red-button.net/): work with a dedicated team of experts to simulate real-world DDoS attack scenarios in a controlled environment.
 - [RedWolf](https://www.redwolfsecurity.com/services/#cloud-ddos) a self-service or guided DDoS testing provider with real-time control.
+- [MazeBolt](https://mazebolt.com):The RADAR™ platform continuously identifies and enables the elimination of DDoS vulnerabilities – proactively and with zero disruption to business operations.
 
 Our testing partners' simulation environments are built within Azure. You can only simulate against Azure-hosted public IP addresses that belong to an Azure subscription of your own, which will be validated by our partners before testing. Additionally, these target public IP addresses must be protected under Azure DDoS Protection. Simulation testing allows you to assess your current state of readiness, identify gaps in your incident response procedures, and guide you in developing a proper [DDoS response strategy](ddos-response-strategy.md). 
 

articles/governance/machine-configuration/whats-new/migrating-from-azure-automation.md

@@ -102,7 +102,7 @@ $getParams = @{
     AutomationAccountName = '<your-automation-account-name>'
 }
 
-Get-AzAutomationDscConfiguration @params
+Get-AzAutomationDscConfiguration @getParams
 ```
 
 ```Output

articles/operator-insights/ingestion-agent-release-notes.md

@@ -17,7 +17,9 @@ This page is updated for each new release of the ingestion agent, so revisit it
 
 ## Version 2.0.0 - March 2024
 
-Download for [RHEL8](https://download.microsoft.com/download/8/2/7/82777410-04a8-4219-a8c8-2f2ea1d239c4/az-aoi-ingestion-2.0.0-1.el8.x86_64.rpm).
+Supported distributions: 
+- RHEL 8
+- RHEL 9
 
 ### Known issues
 
@@ -34,7 +36,9 @@ None
 
 ## Version 1.0.0 - February 2024
 
-Download for [RHEL8](https://download.microsoft.com/download/c/6/c/c6c49e4b-dbb8-4d00-be7f-f6916183b6ac/az-aoi-ingestion-1.0.0-1.el8.x86_64.rpm).
+Supported distributions: 
+- RHEL 8
+- RHEL 9
 
 ### Known issues
 

articles/operator-insights/set-up-ingestion-agent.md

@@ -65,34 +65,6 @@ We recommend that you restrict the following:
 
 When using an Azure VM, also follow all recommendations from Microsoft Defender for Cloud. You can find these recommendations in the portal by navigating to the VM, then selecting Security.
 
-## Download the RPM for the agent
-
-Download the RPM for the ingestion agent using the details you received as part of the [Azure Operator Insights onboarding process](overview.md#how-do-i-get-access-to-azure-operator-insights) or from [https://go.microsoft.com/fwlink/?linkid=2260508](https://go.microsoft.com/fwlink/?linkid=2260508).
-
-Links to the current and previous releases of the agents are available below the heading of each [release note](ingestion-agent-release-notes.md). If you're looking for an agent version that's more than six months old, check out the [release notes archive](ingestion-agent-release-notes-archive.md).
-
-### Verify the authenticity of the ingestion agent RPM (optional)
-
-Before you install the RPM, you can verify the signature of the RPM with the [Microsoft public key file](https://packages.microsoft.com/keys/microsoft.asc) to ensure it hasn't been corrupted or tampered with.
-
-To do this, perform the following steps:
-
-1. Download the RPM.
-1. Download the provided public key
-    ```
-    wget https://packages.microsoft.com/keys/microsoft.asc
-    ```
-1. Import the public key to the GPG keyring
-    ```
-    gpg --import microsoft.asc
-    ```
-1. Verify the RPM signature matches the public key
-    ```
-    rpm --checksig <path-to-rpm>
-    ```
-
-The output of the final command should be `<path-to-rpm>: digests signatures OK`
-
 ## Set up authentication to Azure
 
 The ingestion agent must be able to authenticate with the Azure Key Vault created by the Data Product to retrieve storage credentials. The method of authentication can either be:
@@ -186,7 +158,6 @@ Repeat these steps for each VM onto which you want to install the agent.
     ```
     sudo dnf install systemd logrotate zip
     ```
-1. Obtain the ingestion agent RPM and copy it to the VM.
 1. If you're using a service principal, copy the base64-encoded P12 certificate (created in the [Prepare certificates](#prepare-certificates-for-the-service-principal) step) to the VM, in a location accessible to the ingestion agent.
 1. Configure the agent VM based on the type of ingestion source.
 
@@ -222,22 +193,26 @@ Repeat these steps for each VM onto which you want to install the agent.
 
     ---
 
-## Ensure that VM can resolve Microsoft hostnames
+## Ensure that the VM can resolve Microsoft hostnames
 
 Check that the VM can resolve public hostnames to IP addresses. For example, open an SSH session and use `dig login.microsoftonline.com` to check that the VM can resolve `login.microsoftonline.com` to an IP address.
 
 If the VM can't use DNS to resolve public Microsoft hostnames to IP addresses, [map the required hostnames to IP addresses](map-hostnames-ip-addresses.md). Return to this procedure when you have finished the configuration.
 
 ## Install the agent software
 
-Repeat these steps for each VM onto which you want to install the agent:
+The agent software package is hosted on the "Linux software repository for Microsoft products" at [https://packages.microsoft.com](https://packages.microsoft.com)
 
-1. In an SSH session, change to the directory where the RPM was copied.
-1. Install the RPM.
-    ```
-    sudo dnf install ./*.rpm
-    ```
-    Answer `y` when prompted. If there are any missing dependencies, the RPM won't be installed.
+**The name of the ingestion agent package is `az-aoi-ingestion`.**
+
+To download and install a package from the software repository, follow the relevant steps for your VM's Linux distribution in [
+How to install Microsoft software packages using the Linux Repository](/linux/packages#how-to-install-microsoft-software-packages-using-the-linux-repository).
+
+ For example, if you are installing on a VM running Red Hat Enterprise Linux (RHEL) 8, follow the instructions under the [Red Hat-based Linux distributions](/linux/packages#red-hat-based-linux-distributions) heading, substituting the following parameters:
+
+- distribution:  `rhel`
+- version: `8`
+- package-name: `az-aoi-ingestion`
 
 ## Configure the agent software
 
@@ -344,7 +319,6 @@ The configuration you need is specific to the type of source and your Data Produ
     ```    
     sudo systemctl enable az-aoi-ingestion.service
     ```
-1. Save a copy of the delivered RPM – you need it to reinstall or to back out any future upgrades.
 
 ## Related content
 

articles/operator-insights/upgrade-ingestion-agent.md

@@ -14,49 +14,31 @@ ms.date: 02/29/2024
 
 The ingestion agent is a software package that is installed onto a Linux Virtual Machine (VM) owned and managed by you. You might need to upgrade the agent.
 
-In this article, you'll upgrade your ingestion agent and roll back an upgrade.
+This article describes how to upgrade your ingestion agent, and how to roll back an upgrade.
 
 ## Prerequisites
 
-Obtain the latest version of the ingestion agent RPM from [https://go.microsoft.com/fwlink/?linkid=2260508](https://go.microsoft.com/fwlink/?linkid=2260508).
+Decide which version of the ingestion agent you would like to upgrade to. If you don't specify a version when you upgrade, you'll upgrade to the most recent version.
 
-Links to the current and previous releases of the agents are available below the heading of each [release note](ingestion-agent-release-notes.md). If you're looking for an agent version that's more than 6 months old, check out the [release notes archive](ingestion-agent-release-notes-archive.md).
+See [What's new with Azure Operator Insights ingestion agent](ingestion-agent-release-notes.md) for a list of recent releases and to see what's changed in each version. If you're looking for an agent version that's more than six months old, check out the [release notes archive](ingestion-agent-release-notes-archive.md).
 
-### Verify the authenticity of the ingestion agent RPM (optional)
-
-Before you install the RPM, you can verify the signature of the RPM with the [Microsoft public key file](https://packages.microsoft.com/keys/microsoft.asc) to ensure it has not been corrupted or tampered with.
-
-To do this, perform the following steps:
-
-1. Download the RPM.
-1. Download the provided public key
-    ```
-    wget https://packages.microsoft.com/keys/microsoft.asc
-    ```
-1. Import the public key to the GPG keyring
-    ```
-    gpg --import microsoft.asc
-    ```
-1. Verify the RPM signature matches the public key
-    ```
-    rpm --checksig <path-to-rpm>
-    ```
-
-The output of the final command should be `<path-to-rpm>: digests signatures OK`
+If you would like to verify the authenticity of the ingestion agent package before upgrading, see [How to use the GPG Repository Signing Key](/linux/packages#how-to-use-the-gpg-repository-signing-key).
 
 ## Upgrade the agent software
 
 To upgrade to a new release of the agent, repeat the following steps on each VM that has the old agent.
 
-1. Ensure you have a copy of the currently running version of the RPM, in case you need to roll back the upgrade.
-1. Copy the new RPM to the VM.
-1. Connect to the VM over SSH, and change to the directory where the RPM was copied.
+1. Connect to the VM over SSH.
 1. Save a copy of the existing */etc/az-aoi-ingestion/config.yaml* configuration file.
-1. Upgrade the RPM.
+1. Upgrade the agent using your VM's package manager. For example, for Red Hat-based Linux Distributions:
+    ```
+    sudo dnf upgrade az-aoi-ingestion
     ```
-    sudo dnf install ./*.rpm
+    Answer `y` when prompted.
+    1. Alternatively, to upgrade to a specific version of the agent, specify the version number in the command. For example, for version 2.0.0 on a RHEL8 system, use the following command:
+    ```
+    sudo dnf install az-aoi-ingestion-2.0.0
     ```
-    Answer `y` when prompted.  
 1. Make any changes to the configuration file described by your support contact or the documentation for the new version. Most upgrades don't require any configuration changes.
 1. Restart the agent.
     ```
@@ -72,8 +54,11 @@ To upgrade to a new release of the agent, repeat the following steps on each VM
 
 If an upgrade or configuration change fails:
 
+1. Downgrade back to the previous version by reinstalling the previous version of the agent. For example, to downgrade to version 1.0.0 on a RHEL8 system, use the following command:
+    ```
+    sudo dnf downgrade az-aoi-ingestion-1.0.0
+    ```
 1. Copy the backed-up configuration file from before the change to the */etc/az-aoi-ingestion/config.yaml* file.
-1. Downgrade back to the original RPM.
 1. Restart the agent.
     ```
     sudo systemctl restart az-aoi-ingestion.service