See solution below.
Explanation:
To enable streaming of diagnostic telemetry for a single or a pooled database, follow these steps:
1. Go to Azure SQL database resource.
2. Select Diagnostics settings.
3.Select Turn on diagnostics if no previous settings exist, or select Edit setting to edit a previous setting. You can create up to three parallel connections to stream diagnostic telemetry.
4. Select Add diagnostic setting to configure parallel streaming ofdiagnostics data to multiple resources.

5. Enter a setting name for your own reference.
6. Select a destination resource for the streaming diagnostics data: Archive to storage account, Stream to an event hub, or Send to Log Analytics.
7. For the standard, event-based monitoring experience, select the following check boxes for database diagnostics log telemetry: QueryStoreRuntimeStatistics

8. For an advanced, one-minute-based monitoring experience, select the check box for Basic metrics.
9. SelectSave.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/metrics-diagnostic-telemetry-logging-streaming- export-configure

The following table provide a quick comparison of the Azure Monitor agents for Windows.

Reference:
https: //docs.mic rosoft.com/en-us/azure/azure-monitor/platform/agents-overview

Instead you should deploy an Azureself-hosted agent to an on-premises server.
Note: To build your code or deploy your software using Azure Pipelines, you need at least one agent.
If your on-premises environments do not have connectivity to a Microsoft-hosted agent pool (which is typically the case due to intermediate firewalls), you'll need to manually configure a self-hosted agent on on- premises computer(s).
Note 2: As we [Microsoft] are launching this new experience in preview, we are currently optimizing it for Azure Kubernetes Service (AKS) and Azure Container Registry (ACR). Other Kubernetes clusters, for example running on-premises or in other clouds, as well as other container registries, can be used, but require setting up a Service Account and connection manually.
References:
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops

See solution below.
Explanation:
You can usea system-assigned managed identity for a Windows virtual machine (VM) to access Azure Key Vault.
Sign in to Azure portal
Locate virtual machine VM1.
Select Identity
Enable the system-assigned identity for VM1 by setting the Status to On.

Note:Enabling a system-assigned managed identity is a one-click experience. You can either enable it during the creation of a VM or in the properties of an existing VM.
Reference:
https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad

Explanation:
https://docs.microsoft.com/en-us/azure/devops/migrate/security-validation-cicd-pipeline?view=azure-devops
& viewFallbackFrom=vsts
So:
PR: Static Code Analysis
CI: Static Code Analysis
CD: PenTest