Merge branch 'MicrosoftDocs:main' into main

Author: eak13

articles/active-directory/app-provisioning/on-premises-web-services-connector.md

@@ -40,7 +40,7 @@ The web services connector implements the following functionalities:
 
 
 ##  Documentation for popular applications
-Integrations with popular applications such as SAP ECC and Oracle eBusiness Suite can be found [here](https://www.microsoft.com/download/details.aspx?id=51495). You can also configure a template to connect to your own [rest or SOAP API](/microsoft-identity-manager/reference/microsoft-identity-manager-2016-ma-ws).
+Integrations with popular applications such as [SAP ECC 7.0](on-premises-sap-connector-configure.md) and Oracle eBusiness Suite can be found [here](https://www.microsoft.com/download/details.aspx?id=51495). You can also configure a template to connect to your own [rest or SOAP API](/microsoft-identity-manager/reference/microsoft-identity-manager-2016-ma-ws).
 
 
 For more information, see [the Overview of the generic Web Service connector](/microsoft-identity-manager/reference/microsoft-identity-manager-2016-ma-ws) in the MIM documentation library.

articles/active-directory/devices/manage-device-identities.md

@@ -118,6 +118,8 @@ In this preview, you have the ability to infinitely scroll, reorder columns, and
 - Join type (Azure AD joined, Hybrid Azure AD joined, Azure AD registered)
 - Activity timestamp
 - OS Type and Version
+   - Windows is displayed for Windows 11 and Windows 10 devices (with KB5006738).
+   - Windows Server is displayed for [supported versions managed with Microsoft Defender for Endpoint](/mem/intune/protect/mde-security-integration#supported-platforms).
 - Device type (printer, secure VM, shared device, registered device)
 - MDM
 - Autopilot

articles/azure-monitor/essentials/rest-api-walkthrough.md

@@ -174,6 +174,15 @@ The result should be similar to the following example:
 >
 ---
 
+## API endpoints
+
+The API endpoints use the following pattern:  
+`/<resource URI>/providers/microsoft.insights/<metrics|metricDefinitions>?api-version=<apiVersion>`  
+The `resource URI` is composed of the following components:  
+`/subscriptions/<subscription id>/resourcegroups/<resourceGroupName>/providers/<resourceProviderNamespace>/<resourceType>/<resourceName>/`
+
+> [!IMPORTANT]
+> Be sure to include `/providers/microsoft.insights/` after the resource URI when you make an API call to retrieve metrics or metric definitions.
 ## Retrieve metric definitions
 
 Use the [Azure Monitor Metric Definitions REST API](/rest/api/monitor/metricdefinitions) to access the list of metrics that are available for a service.
@@ -400,7 +409,7 @@ Content-Type: application/json
 Authorization: Bearer <access token>
 ```
 
-The following example retrieves the top three APIs,  by the number of `Transactions` in descending value order, during a 5-minute range, where  the `GeoType` dimension has a value of `Primary`.
+The following example retrieves the top three APIs,  by the number of `Transactions` in descending value order, during a 5-minute range, where the `GeoType` dimension has a value of `Primary`.
 
 ```curl
 curl --location --request GET 'https://management.azure.com/subscriptions/12345678-abcd-98765432-abcdef012345/resourceGroups/azmon-rest-api-walkthrough/providers/Microsoft.Storage/storageAccounts/ContosoStorage/providers/microsoft.insights/metrics \
@@ -485,12 +494,12 @@ There are some important differences between querying metrics for multiple and i
 
 ### Querying metrics for multiple resources examples
 
-The following example shows an individual metricdefinitions request:
+The following example shows an individual metric definitions request:
 ```
 GET https://management.azure.com/subscriptions/12345678-abcd-98765432-abcdef012345/resourceGroups/EASTUS-TESTING/providers/Microsoft.Compute/virtualMachines/TestVM1/providers/microsoft.insights/metricdefinitions?api-version=2021-05-01
 ```
 
-The following request shows the equivalent metricdefinitions request for multiple resources.
+The following request shows the equivalent metric definitions request for multiple resources.
 The only changes are the subscription path instead of a resource ID path, and the addition of `region` and `metricNamespace` query parameters.
 ```
 GET https://management.azure.com/subscriptions/12345678-abcd-98765432-abcdef012345/providers/microsoft.insights/metricdefinitions?api-version=2021-05-01&region=eastus&metricNamespace=microsoft.compute/virtualmachines
@@ -505,7 +514,7 @@ Below is an equivalent metrics request for multiple resources:
 ```
 GET https://management.azure.com/subscriptions/12345678-abcd-98765432-abcdef012345/providers/microsoft.Insights/metrics?timespan=2023-06-25T22:20:00.000Z/2023-06-26T22:25:00.000Z&interval=PT5M&metricnames=Percentage CPU&aggregation=average&api-version=2021-05-01&region=eastus&metricNamespace=microsoft.compute/virtualmachines&$filter=Microsoft.ResourceId eq '*'
 ```
-Note that  a `Microsoft.ResourceId eq '*'` filter is added for the multi resource metrics requests as well. The filter tells the API to return a separate time series per virtual machine resource in the subscription and region. Without the filter the API would return a single time series aggregating the average CPU for all VMs. The times series for each resource is differentiated by the `Microsoft.ResourceId` metadata value on each time series entry, as can be seen in the following sample return value.
+Note that a `Microsoft.ResourceId eq '*'` filter is added for the multi resource metrics requests as well. The filter tells the API to return a separate time series per virtual machine resource in the subscription and region. Without the filter the API would return a single time series aggregating the average CPU for all VMs. The times series for each resource is differentiated by the `Microsoft.ResourceId` metadata value on each time series entry, as can be seen in the following sample return value.
 
 ```JSON
 {
@@ -633,7 +642,7 @@ Note that  a `Microsoft.ResourceId eq '*'` filter is added for the multi resourc
 ### Troubleshooting querying metrics for multiple resources
 
 + No data returned can be due to the wrong region being specified:
-    The multi resource APIs do not verify that any valid resources exist in the specified region and subscription combination. The only indicator that the region may be wrong is getting an empty time series data response. For example: `"timeseries": [],`
+    The multi resource APIs don't verify that any valid resources exist in the specified region and subscription combination. The only indicator that the region may be wrong is getting an empty time series data response. For example: `"timeseries": [],`
 + 401 authorization errors:
     The individual resource metrics APIs requires a user have the [Monitoring Reader](../../role-based-access-control/built-in-roles.md#monitoring-reader) permission on the resource being queried. Because the multi resource metrics APIs are subscription level APIs, users must have the  [Monitoring Reader](../../role-based-access-control/built-in-roles.md#monitoring-reader) permission for the queried subscription to use the multi resource metrics APIs. Even if users have Monitoring Reader on all the resources in a subscription, the request fails if the user doesn't have Monitoring Reader on the subscription itself.
 

articles/azure-monitor/whats-new.md

@@ -16,6 +16,32 @@ This article lists significant changes to Azure Monitor documentation.
 >
 > !["An rss icon"](./media//whats-new/rss.png)  https://aka.ms/azmon/rss
 
+## July 2023
+
+|Subservice| Article | Description |
+|---|---|---|
+Agents|[Azure Monitor Agent Health (Preview)](agents/azure-monitor-agent-health.md)|Introduced a new Azure Monitor Agent Health workbook, which monitors the health of agents deployed across your organization. |
+Alerts|[Manage your alert instances](alerts/alerts-manage-alert-instances.md)|View alerts as a timeline (preview)|
+Alerts|[Upgrade to the Log Alerts API from the legacy Log Analytics alerts API](alerts/alerts-log-api-switch.md)|Changes to the log alert rule creation experience|
+Application-Insights|[Migrate to workspace-based Application Insights resources](app/convert-classic-resource.md)|We now support migrating classic components to workspace-based components via PowerShell cmdlet. |
+Application-Insights|[EventCounters introduction](app/eventcounters.md)|Code samples have been provided for the latest .NET versions.|
+Application-Insights|[Enable a framework extension for Application Insights JavaScript SDK](app/javascript-framework-extensions.md)|We've added a section for the React Native Manual Device Plugin, and clarified exception tracking and device info collection.|
+Application-Insights|[Migrate availability tests](app/availability-test-migration.md)|Migrate your classic URL ping tests to the new standard availability tests using this prescriptive guidance.|
+Application-Insights|[Enable a framework extension for Application Insights JavaScript SDK](app/javascript-framework-extensions.md)|The  'What does the plug-in enable?' and 'Add configuration' sections have been rewritten to align across all of our JavaScript documentation.|
+Application-Insights|[Microsoft Azure Monitor Application Insights JavaScript SDK configuration](app/javascript-sdk-configuration.md)|The  'What does the plug-in enable?' and 'Add configuration' sections have been rewritten to align across all of our JavaScript documentation.|
+Application-Insights|[Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python and Java applications](app/opentelemetry-enable.md)|Clarification of the term "Distro" has been provided.|
+Application-Insights|[Data Collection Basics of Azure Monitor Application Insights](app/opentelemetry-overview.md)|We've added a new article to clarify both manual and automatic instrumentation options to enable Application Insights.|
+Application-Insights|[Enable a framework extension for Application Insights JavaScript SDK](app/javascript-framework-extensions.md)|The "Explore your data" section has been improved.|
+Application-Insights|[Sampling overrides (preview) - Azure Monitor Application Insights for Java](app/java-standalone-sampling-overrides.md)|We've documented steps for troubleshooting sampling.|
+Logs|[Set a table's log data plan to Basic or Analytics](logs/basic-logs-configure.md)|Additional Azure tables now support low-cost basic logs, including tables for the Bare Metal Machines, Managed Lustre, Nexus Clusters, and Nexus Storage Appliances services. |
+Logs|[Create and manage a dedicated cluster in Azure Monitor Logs](logs/logs-dedicated-clusters.md)|The minimum ingestion commitment for a dedicated cluster is now 100 GB per day (previously 500 GB). |
+Logs|[Query Basic Logs in Azure Monitor](logs/basic-logs-query.md)|Basic log queries are now billable.|
+Logs|[Restore logs in Azure Monitor](logs/restore.md)|Restored logs are now billable.|
+Logs|[Run search jobs in Azure Monitor](logs/search-jobs.md)|Search jobs are now billable.|
+Logs|[Tutorial: Ingest events from Azure Event Hubs into Azure Monitor Logs (Preview)](logs/ingest-logs-event-hub.md)|New article that explains how to ingest data directly from Azure Event Hubs, Azure's big data streaming platform, into Azure Monitor Logs.|
+Optimization-Insights|[Monitor and analyze runtime behavior with Code Optimizations (Preview)](insights/code-optimizations.md)|PM added a demo video for Code Optimizations|
+Virtual-Machines|[Migrate from deprecated VM insights policies](vm/vminsights-migrate-deprecated-policies.md)|We're deprecating the VM insights DCR deployment policies and replacing them with new policies because of a race condition issue.This article explains how to migrate from deprecated VM insights policies to their replacement policies.|
+
 ## June 2023
 
 |Subservice| Article | Description |

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -175,7 +175,10 @@ If you use a new VNet, you can create a subnet and delegate the subnet to Azure
 
 If the VNet is peered with another VNet, you can't expand the VNet address space. For that reason, the new delegated subnet needs to be created within the VNet address space. If you need to extend the address space, you must delete the VNet peering before expanding the address space.
 
-Ensure that the address space size of the Azure NetApp Files delegated subnet is smaller than the address space of the virtual network to avoid unforeseen issues.
+>[!IMPORTANT]
+>The address space size of the Azure NetApp Files VNet should be larger than its delegated subnet. If it is not, Azure NetApp Files volume creation will fail in some scenarios.
+>
+> It's also recommended that the size of the delegated subnet be at least /25 for SAP workloads and /26 for other workload scenarios.
 
 ### UDRs and NSGs
 

articles/azure-vmware/rotate-cloudadmin-credentials.md

@@ -30,12 +30,8 @@ Instead of using the cloudadmin user to connect services to vCenter Server, we r
 
 ### [Portal](#tab/azure-portal)
 
-1. In your Azure VMware Solution private cloud, select **Identity**.
-
+1. In your Azure VMware Solution private cloud, select **VMWare credentials**.
 1. Select **Generate new password**.
-
-   :::image type="content" source="media/rotate-cloudadmin-credentials/reset-vcenter-credentials-1.png" alt-text="Screenshot showing the vCenter Server credentials and a way to copy them or generate a new password." lightbox="media/rotate-cloudadmin-credentials/reset-vcenter-credentials-1.png":::
-
 1. Select the confirmation checkbox and then select **Generate password**.
 
 
@@ -53,12 +49,19 @@ To begin using Azure CLI:
    az resource invoke-action --action rotateVcenterPassword --ids "/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroup}/providers/Microsoft.AVS/privateClouds/{PrivateCloudName}" --api-version "2020-07-17-preview"
    ```
 
+
 ---
 
 
 
 
 
+
+
+
+ 
+
+ 
 ## Update HCX Connector 
 
 1. Go to the on-premises HCX Connector at https://{ip of the HCX connector appliance}:443 and sign in using the new credentials.
@@ -73,10 +76,11 @@ To begin using Azure CLI:
 
 4. Provide the new vCenter Server user credentials and select **Edit**, which saves the credentials. Save should show successful.
 
-
 ## Next steps
 
 Now that you've covered resetting your vCenter Server credentials for Azure VMware Solution, you may want to learn about:
 
 - [Integrating Azure native services in Azure VMware Solution](integrate-azure-native-services.md)
 - [Deploying disaster recovery for Azure VMware Solution workloads using VMware HCX](deploy-disaster-recovery-using-vmware-hcx.md)
+
+

articles/event-grid/mqtt-overview.md

@@ -91,6 +91,10 @@ Event Grid allows you to route your MQTT messages to Azure services or webhooks
 
 :::image type="content" source="media/mqtt-overview/routing-high-res.png" alt-text="Diagram of the MQTT message routing." border="false":::
 
+### MQTT Clients Life Cycle Events 
+
+Client Life Cycle events allow applications to react to events about the client connection status or the client resource operations. It allows you to keep track of your client's connection status, react with a mitigation action for client disconnections, and track the namespace that your clients are attached to during automated failovers.Learn more about [MQTT Client Life Cycle Events](mqtt-client-life-cycle-events.md).
+
 ## Next steps
 
 Use the following articles to learn more about the MQTT support in Event Grid and its main concepts.

articles/event-hubs/TOC.yml

@@ -66,12 +66,12 @@
           href: event-hubs-capture-python.md
     - name: Use Schema Registry
       items:
-        - name: Create a schema registry - Azure portal
-          href: create-schema-registry.md  
-        - name: Validate events using an Avro schema (.NET + AMQP)
-          href: schema-registry-dotnet-send-receive-quickstart.md
-        - name: Validate events using an Avro schema (Java + Apache Kafka)
+        - name: Create a schema - Azure portal
+          href: create-schema-registry.md
+        - name: Validate schemas for Kafka applications 
           href: schema-registry-kafka-java-send-receive-quickstart.md
+        - name: Validate schemas with Avro for Event Hubs SDK 
+          href: schema-registry-dotnet-send-receive-quickstart.md
     - name: Create a dedicated cluster
       href: event-hubs-dedicated-cluster-create-portal.md
 - name: Tutorials

articles/governance/policy/concepts/event-overview.md

@@ -16,23 +16,52 @@ pushed through [Azure Event Grid](../../../event-grid/index.yml) to subscribers
 Critically, you only pay for what you use.
 
 Azure Policy events are sent to the Azure Event Grid, which provides reliable delivery services to
-your applications through rich retry policies and dead-letter delivery. To learn more, see
-[Event Grid message delivery and retry](../../../event-grid/delivery-and-retry.md).
-
-The common Azure Policy event scenario is tracking when the compliance state of a resource changes
-during policy evaluation. Event-based architecture is an efficient way to react to these changes
-instead of scanning the compliance state of resources on a fixed schedule.
+your applications through rich retry policies and dead-letter delivery. Event Grid takes 
+care of the proper routing, filtering, and multicasting of the events to destinations via Event Grid subscriptions.
+To learn more, see [Event Grid message delivery and retry](../../../event-grid/delivery-and-retry.md). 
 
 > [!NOTE]
 > Azure Policy state change events are sent to Event Grid after an
 > [evaluation trigger](../how-to/get-compliance-data.md#evaluation-triggers) finishes resource
 > evaluation.
 
+## Event Grid Benefits
+Event Grid has a few benefits for customers and services in the Azure ecosystem: 
+- Automation: To stay current with your policy environment, Event Grid offers an automated mechanism to generate
+  alerts and trigger tasks depending on compliance states.
+- Durable delivery:  In order for services and user applications to respond in real-time to policy compliance events,
+  Event Grid seeks to offer policy events with minimum latency. Event Grid retries transmission of an event if a subscriber's
+  endpoint fails to acknowledge receipt of it or if it doesn't, according to a predetermined retry schedule and retry policy.
+- Custom event producer: Event Grid  event producers and consumers don't need to be Azure or Microsoft services.
+  External applications can receive an alert, show the creation of a remediation task or collect messages on who responds to the
+  state change.	
 See
 [Route policy state change events to Event Grid with Azure CLI](../tutorials/route-state-change-events.md)
 for a full tutorial.
 
-:::image type="content" source="../../../event-grid/media/overview/functional-model.png" alt-text="Event Grid model of sources and handlers" lightbox="../../../event-grid/media/overview/functional-model-big.png":::
+There are two primary entities when using Event Grid: 
+- Events: These events can be anything a user may want to react to that includes if a policy compliance state is
+   created, changed, and deleted of a resource such as a VM or storage accounts.
+- Event Grid Subscriptions: These event subscriptions are user configured entities that direct the proper set of events
+  from a publisher to a subscriber. Event subscriptions can filter events based on the resource path the event
+  originated from and the type of event. Additionally, Event Subscriptions can also filter by scope between
+  Azure subscription and Management group.
+
+A common Azure Policy event scenario is tracking when the compliance state of a resource changes
+during policy evaluation. Event-based architecture is an efficient way to react to these changes
+and aids in the event based reaction to compliance state changes.
+
+Another scenario is to automatically trigger remediation tasks without manually ticking off _create 
+remediation task_ on the policy page. Event Grid checks for compliance state and resources that are currently 
+noncompliant can be remedied. Learn more about [remediation structure](../concepts/remediation-structure.md).
+Remediation requires a managed identity and policies must be in Modify or DeployIfNotExists effect. [Learn more about
+effect types](../how-to/remediate-resources.md).
+
+Additionally, Event Grid is helpful as an audit system to store state changes and understand cause of noncompliance over 
+time. The scenarios for Event Grid are endless and based on the motivation, Event Grid is configurable. 
+
+
+:::image type="content" source="../../../event-grid/media/overview/functional-model.png" alt-text="Screenshot of Event Grid model of sources and handlers." lightbox="../../../event-grid/media/overview/functional-model-big.png":::
 
 [!INCLUDE [policy-events.md](../../../../includes/policy/policy-events.md)]