| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| advisor | Advisor Reference Performance Recommendations | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/advisor/advisor-reference-performance-recommendations.md | Learn more about [Azure Database for PostgreSQL flexible server - Upscale Server Our system shows that you have log_statement enabled, for better performance set it to NONE -Learn more about [Azure Database for PostgreSQL flexible server - Optimize log_statement settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging.md). +Learn more about [Azure Database for PostgreSQL flexible server - Optimize log_statement settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging). ### Optimize log_duration settings for PostgreSQL on Azure Database You may experience potential performance degradation due to logging settings. To optimize these settings, set the log_duration server parameter to OFF. -Learn more about [Learn more about Azure Database for PostgreSQL flexible server - Optimize log_duration settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging.md). +Learn more about [Learn more about Azure Database for PostgreSQL flexible server - Optimize log_duration settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging). ### Optimize log_min_duration settings for PostgreSQL on Azure Database Your log_min_duration server parameter is set to less than 60,000 ms (1 minute), which can lead to potential performance degradation. You can optimize logging settings by setting the log_min_duration_statement parameter to -1. -Learn more about [Azure Database for PostgreSQL flexible server - Optimize log_min_duration settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging.md). +Learn more about [Azure Database for PostgreSQL flexible server - Optimize log_min_duration settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging). ### Optimize log_error_verbosity settings for PostgreSQL on Azure Database Your server has been configured to output VERBOSE error logs. This can be useful for troubleshooting your database, but it can also result in reduced database performance. To improve performance, we recommend changing the log_error_verbosity server parameter to the DEFAULT setting. -Learn more about [Learn more about Azure Database for PostgreSQL flexible server - Optimize log_error_verbosity settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging.md). +Learn more about [Learn more about Azure Database for PostgreSQL flexible server - Optimize log_error_verbosity settings for PostgreSQL on Azure Database](/azure/postgresql/flexible-server/concepts-logging). ### Identify if checkpoints are happening too often to improve PostgreSQL - Flexible Server performance |
| ai-studio | Reference Model Inference Api | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-studio/reference/reference-model-inference-api.md | Models deployed to [serverless API endpoints](../how-to/deploy-models-serverless > * [Meta Llama 3 instruct](../how-to/deploy-models-llama.md) family of models > * [Mistral-Small](../how-to/deploy-models-mistral.md) > * [Mistral-Large](../how-to/deploy-models-mistral.md)+> * [Jais](../how-to/deploy-jais-models.md) family of models +> * [Jamba](../how-to/deploy-models-jamba.md) family of models > * [Phi-3](../how-to/deploy-models-phi-3.md) family of models Models deployed to [managed inference](../concepts/deployments-overview.md): Models deployed to [managed inference](../concepts/deployments-overview.md): The API is compatible with Azure OpenAI model deployments. +> [!NOTE] +> The Azure AI model inference API is available in managed inference (Managed Online Endpoints) for __models deployed after June 24th, 2024__. To take advance of the API, redeploy your endpoint if the model has been deployed before such date. + ## Capabilities The following section describes some of the capabilities the API exposes. For a full specification of the API, view the [reference section](reference-model-inference-info.md). |
| aks | Azure Blob Csi | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/azure-blob-csi.md | Azure Blob storage CSI driver supports the following features: ## Before you begin -- You need the Azure CLI version 2.42 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].+- Make sure that you have the Azure CLI version 2.42 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli]. If you have installed the Azure CLI `aks-preview` extension, make sure that you update the extension to the latest version by calling `az extension update --name aks-preview`. - Perform the steps in this [link][csi-blob-storage-open-source-driver-uninstall-steps] if you previously installed the [CSI Blob Storage open-source driver][csi-blob-storage-open-source-driver] to access Azure Blob storage from your cluster. > [!NOTE] |
| azure-functions | Functions Dotnet Class Library | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-dotnet-class-library.md | The following is an example of a minimal `local.settings.json` file with these c } ``` -You might need to make other changes to your app based on the version support of its dependencies. +If your app uses [`Microsoft.Azure.DurableTask.Netherite.AzureFunctions`](https://www.nuget.org/packages/Microsoft.Azure.DurableTask.Netherite.AzureFunctions), ensure it targets version 1.5.3 or later. Due to a behavior change in .NET 8, apps with older versions of the package will throw an ambiguous constructor exception. ++You might need to make other changes to your app based on the version support of its other dependencies. ## Functions class library project |
| azure-monitor | Alerts Common Schema | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/alerts-common-schema.md | For sample alerts that use the common schema, see [Sample alert payloads](alerts | firedDateTime | The date and time when the alert instance was fired in Coordinated Universal Time (UTC). | | resolvedDateTime | The date and time when the monitor condition for the alert instance is set to **Resolved** in UTC. Currently only applicable for metric alerts.| | description | The description, as defined in the alert rule. |+| alertRuleID | The ID of the alert rule that generated the alert instance.| +| resourceType | The resource type affected by the alert.| +| resourceGroupName | Name of the resource group for the impacted resource.| |essentialsVersion| The version number for the essentials section.| |alertContextVersion | The version number for the `alertContext` section.| |investigationLink | Link to investigate the alert in Azure Monitor. Currently requires limited preview registration.| |
| azure-monitor | Basic Logs Configure | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/basic-logs-configure.md | All custom tables created with or migrated to the [data collection rule (DCR)-ba | Kubernetes services | [AKSAudit](/azure/azure-monitor/reference/tables/AKSAudit)<br>[AKSAuditAdmin](/azure/azure-monitor/reference/tables/AKSAuditAdmin)<br>[AKSControlPlane](/azure/azure-monitor/reference/tables/AKSControlPlane) | | Log Analytics | [LASummaryLogs](/azure/azure-monitor/reference/tables/LASummaryLogs) | | Managed Lustre | [AFSAuditLogs](/azure/azure-monitor/reference/tables/AFSAuditLogs) |-| Managed NGINX | [NGXOperationLogs](/azure/azure-monitor/reference/tables/ngxoperationlogs) | +| Managed NGINX | [NGXOperationLogs](/azure/azure-monitor/reference/tables/ngxoperationlogs) <br>[NGXSecurityLogs](/azure/azure-monitor/reference/tables/ngxsecuritylogs)| | Media Services | [AMSLiveEventOperations](/azure/azure-monitor/reference/tables/AMSLiveEventOperations)<br>[AMSKeyDeliveryRequests](/azure/azure-monitor/reference/tables/AMSKeyDeliveryRequests)<br>[AMSMediaAccountHealth](/azure/azure-monitor/reference/tables/AMSMediaAccountHealth)<br>[AMSStreamingEndpointRequests](/azure/azure-monitor/reference/tables/AMSStreamingEndpointRequests) | | Microsoft Graph | [MicrosoftGraphActivityLogs](/azure/azure-monitor/reference/tables/microsoftgraphactivitylogs) | | Monitor | [AzureMetricsV2](/azure/azure-monitor/reference/tables/AzureMetricsV2) | |
| azure-monitor | Summary Rules | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/summary-rules.md | Instead of logging hundreds of similar entries within an hour, the destination t ## Pricing model -Summary rules don't have a direct cost, and you only pay for the query on the source table(s) and the ingestion to the destination table: +There is no direct cost for Summary rules, and you only pay for the query on the source table and the results ingestion to the destination table: -| Source table plan | Query cost | Query results ingestion cost | +| Source table plan | Query cost | Summary results ingestion cost | | | | | | Analytics | No cost | Analytics ingested GB | | Basic | Scanned GB | Analytics ingested GB | |
| cloud-shell | Pricing | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/cloud-shell/pricing.md | Cloud Shell requires a Microsoft Azure Files share. ## Storage cost -Cloud Shell requires a new or existing Azure Files share to be mounted to persist files across -sessions. Storage incurs regular costs. For pricing information, see [Azure Files Pricing][01]. +If you would like to persist files across sessions, Cloud Shell requires a new or existing Azure +Files share to be mounted. Storage incurs regular costs. For pricing information, see +[Azure Files Pricing][01]. ## Network costs |
| defender-for-iot | Dell Poweredge R340 Xl Legacy | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/defender-for-iot/organizations/appliance-catalog/dell-poweredge-r340-xl-legacy.md | Configure the appliance BIOS only if you didn't purchase your appliance from Arr 1. Select **Boot Settings**. -1. For the **Boot Mode** option, select **BIOS**. +1. For the **Boot Mode** option, select **UEFI**. 1. Select **Back**, and then select **Finish** to exit the BIOS settings. |
| defender-for-iot | Hpe Proliant Dl20 Plus Smb | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/defender-for-iot/organizations/appliance-catalog/hpe-proliant-dl20-plus-smb.md | Installation includes: - Enabling remote access and updating the default administrator password - Configuring iLO port on network port 1-- Configuring BIOS and RAID1 settings+- Configuring BIOS settings - Installing Defender for IoT software > [!NOTE] This procedure describes how to update the HPE BIOS configuration for your OT de 1. Select **Esc** twice to close the **System Configuration** form. -1. Select **Embedded RAID 1: HPE Smart Array E208i-a SR Gen 10** > **Array Configuration** > **Create Array**. --1. Select **Proceed to Next Form**. --1. In the **Set RAID Level** form, set the level to **RAID 1**. - 1. Select **Proceed to Next Form**. 1. In the **Logical Drive Label** form, enter **Logical Drive 1**. |
| mysql | Whats Happening To Mysql Single Server | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/mysql/migrate/whats-happening-to-mysql-single-server.md | -**Azure Database for MySQL - Single Server is on the retirement path** and is scheduled for retirement by **September 16, 2024**. +> [!IMPORTANT] +> **Azure Database for MySQL - Single Server is on the retirement path** and is scheduled for retirement by **September 16, 2024**. As part of this retirement, we'll no longer support creating new Single Server instances from the Azure portal beginning **January 16, 2023** and Azure CLI beginning **March 19, 2024**. If you still need to create Single Server instances to meet business continuity needs, raise an Azure support ticket. You'll still be able to create read replicas and perform restores (PITR and geo-restore) for your existing single server instance and this will continue to be supported until the sunset date of **September 16, 2024**. |
| mysql | Select Right Deployment Type | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/mysql/select-right-deployment-type.md | When making your decision, consider the following two options: - [Flexible Server](flexible-server/overview.md) is a fully managed production-ready database service designed for more granular control and flexibility over database management functions and configuration settings. The flexible server architecture allows users to opt for high availability within a single availability zone and across multiple availability zones. Flexible servers provide better cost optimization controls with the ability to stop/start the server and burstable compute tier, ideal for workloads that don't need full compute capacity continuously. Flexible Server also supports reserved instances allowing you to save up to 63% cost, which is ideal for production workloads with predictable compute capacity requirements. The service supports the community version of MySQL 5.7 and 8.0. The service is generally available today in various [Azure regions](flexible-server/overview.md#azure-regions). Flexible servers are best suited for all new developments and migration of production workloads to Azure Database for MySQL service. - - [Single Server](single-server/single-server-overview.md) is a fully managed database service designed for minimal customization. The single server platform is designed to handle most database management functions such as patching, backups, high availability, and security with minimal user configuration and control. The architecture is optimized for built-in high availability with 99.99% availability in a single availability zone. It supports the community version of MySQL 5.6 (retired), 5.7, and 8.0. The service is generally available today in various [Azure regions](https://azure.microsoft.com/global-infrastructure/services/). Single servers are best-suited **only for existing applications already leveraging single servers**. It's recommended to choose Flexible Server for all new developments or migrations. - - **MySQL on Azure VMs**. This option falls into the industry category of IaaS. With this service, you can run MySQL Server inside a managed virtual machine on the Azure cloud platform. You can install all recent versions and editions of MySQL on a virtual machine. ## Compare the MySQL deployment options in Azure |
| nat-gateway | Nat Metrics | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/nat-gateway/nat-metrics.md | To create the alert, use the following steps: 1. Select **Create** to create the alert rule. >[!NOTE]->SNAT port exhaustion on your NAT gateway resource is uncommon. If you see SNAT port exhaustion, check if NAT gateway's idle timeout timer is set higher than the default amount of 4 minutes. A long idle timeout timer seeting can cause SNAT ports too be in hold down for longer, which results in exhausting SNAT port inventory sooner. You can also scale your NAT gateway with additional public IPs to increase NAT gateway's overall SNAT port inventory. To troubleshoot these kinds of issues, refer to the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity#snat-exhaustion-due-to-nat-gateway-configuration). +>SNAT port exhaustion on your NAT gateway resource is uncommon. If you see SNAT port exhaustion, check if NAT gateway's idle timeout timer is set higher than the default amount of 4 minutes. A long idle timeout timer setting can cause SNAT ports too be in hold down for longer, which results in exhausting SNAT port inventory sooner. You can also scale your NAT gateway with additional public IPs to increase NAT gateway's overall SNAT port inventory. To troubleshoot these kinds of issues, refer to the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity#snat-exhaustion-due-to-nat-gateway-configuration). ### Alerts for NAT gateway resource health |
| operator-nexus | Concepts Security Access Identity | https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/operator-nexus/concepts-security-access-identity.md | -Azure role-based access control (Azure RBAC) is an authorization system built on [Azure Resource Manager](../azure-resource-manager/management/overview.md) that provides fine-grained access management of Azure resources. +Azure role-based access control (Azure RBAC) is an authorization system built +on [Azure Resource Manager](../azure-resource-manager/management/overview.md) that +provides fine-grained access management of Azure resources. -The Azure RBAC model allows users to set permissions on different scope levels: management group, subscription, resource group, or individual resources. Azure RBAC for key vault also allows users to have separate permissions on individual keys, secrets, and certificates +The Azure RBAC model allows users to set permissions on different scope levels: management +group, subscription, resource group, or individual resources. Azure RBAC for key +vault also allows users to have separate permissions on individual keys, secrets, +and certificates. For more information, see [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md). -#### Built-in roles +## Operator Nexus built-in roles Azure Operator Nexus provides the following built-in roles. -| Role | Description | -|-|--| -| Operator Nexus Keyset Administrator Role (Preview) | Manage interactive access to Azure Operator Nexus Compute resources by adding, removing, and updating baremetal machine (BMM) and baseboard management (BMC) keysets. | -| | | +[Operator Nexus Compute Contributor Role (Preview)](#operator-nexus-compute-contributor-role-preview) ++[Operator Nexus Keyset Administrator Role (Preview)](#operator-nexus-keyset-administrator-role-preview) ++> [!NOTE] +> Preview roles are subject to change. ++++### Operator Nexus Compute Contributor Role (Preview) ++The user with this role can have full access to manage and configure Nexus resources, +including creating, modifying, and deleting resources related to Nexus infrastructure. ++| Actions | Description | +||--| +| Microsoft.Authorization/*/read | Read roles and role assignments | +| Microsoft.ExtendedLocation/customLocations/deploy/action | Deploy permissions to a Custom Location resource | +| Microsoft.ExtendedLocation/customLocations/read | Gets a Custom Location resource | +| Microsoft.HybridCompute/machines/extensions/read | Reads any Azure Arc extensions | +| Microsoft.HybridCompute/machines/read | Read any Azure Arc machines | +| Microsoft.Insights/alertRules/* | Create and manage a classic metric alert | +| Microsoft.Kubernetes/connectedClusters/read | Read connectedClusters | +| Microsoft.KubernetesConfiguration/extensions/read | Gets extension instance resource | +| Microsoft.ManagedNetworkFabric/networkFabricControllers/join/action | Join action for Network Fabric Controller resource. | +| Microsoft.ManagedNetworkFabric/networkFabrics/join/action | Join action for Network Fabric resource. | +| Microsoft.ManagedNetworkFabric/networkRacks/join/action | Join action for Network Rack resource. | +| Microsoft.NetworkCloud/bareMetalMachines/cordon/action | Cordon the provided bare metal machine's Kubernetes node | +| Microsoft.NetworkCloud/bareMetalMachines/delete | Delete the provided bare metal machine. All customer initiated requests will be rejected as the life cycle of this resource is managed by the system. | +| Microsoft.NetworkCloud/bareMetalMachines/powerOff/action | Power off the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/read | Get properties of the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/reimage/action | Reimage the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/replace/action | Replace the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/restart/action | Restart the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/runDataExtracts/action | Run one or more data extractions on the provided bare metal machine. | +| Microsoft.NetworkCloud/bareMetalMachines/runReadCommands/action | Run one or more read-only commands on the provided bare metal machine. | +| Microsoft.NetworkCloud/bareMetalMachines/start/action | Start the provided bare metal machine | +| Microsoft.NetworkCloud/bareMetalMachines/uncordon/action | Uncordon the provided bare metal machine's Kubernetes node | +| Microsoft.NetworkCloud/bareMetalMachines/write | Create a new bare metal machine or update the properties of the existing one. All customer initiated requests will be rejected while life cycling the resource. | +| Microsoft.NetworkCloud/clusterManagers/delete | Delete the provided cluster manager | +| Microsoft.NetworkCloud/clusterManagers/read | Get the properties of the provided cluster manager | +| Microsoft.NetworkCloud/clusterManagers/write | Create a new cluster manager or update properties of the cluster manager if it exists | +| Microsoft.NetworkCloud/clusters/bareMetalMachineKeySets/read | Get bare metal machine key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bmcKeySets/read | Get baseboard management controller key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/continueUpdateVersion/action | Trigger the continuation of an update for a cluster with a matching update strategy that has paused after completing a segment of the update | +| Microsoft.NetworkCloud/clusters/delete | Delete the provided cluster | +| Microsoft.NetworkCloud/clusters/deploy/action | Deploy the cluster using the rack configuration provided during creation | +| Microsoft.NetworkCloud/clusters/metricsConfigurations/delete | Delete the metrics configuration of the provided cluster | +| Microsoft.NetworkCloud/clusters/metricsConfigurations/read | Get metrics configuration of the provided cluster | +| Microsoft.NetworkCloud/clusters/metricsConfigurations/write | Create new or update the existing metrics configuration of the provided cluster | +| Microsoft.NetworkCloud/clusters/read | Get properties of the provided cluster | +| Microsoft.NetworkCloud/clusters/scanRuntime/action | Triggers the execution of a runtime protection scan to detect and remediate detected issues, in accordance with the cluster configuration | +| Microsoft.NetworkCloud/clusters/updateVersion/action | Update the version of the provided cluster to one of the available supported versions | +| Microsoft.NetworkCloud/clusters/write | Create a new cluster or update the properties of the cluster if it exists | +| Microsoft.NetworkCloud/locations/operationStatuses/read | Read operation status | +| Microsoft.NetworkCloud/operations/read | Read operation | +| Microsoft.NetworkCloud/rackSkus/read | Get the properties of the provided rack SKU | +| Microsoft.NetworkCloud/racks/delete | Delete the provided rack. All customer initiated requests will be rejected as the life cycle of this resource is managed by the system | +| Microsoft.NetworkCloud/racks/join/action | Join a Nexus rack | +| Microsoft.NetworkCloud/racks/read | Get properties of the provided rack | +| Microsoft.NetworkCloud/racks/write | Create a new rack or update properties of the existing one. All customer initiated requests will be rejected as the life cycle of this resource is managed by the system | +| Microsoft.NetworkCloud/register/action | Register the subscription for Microsoft.NetworkCloud | +| Microsoft.NetworkCloud/registeredSubscriptions/read | Read registered subscriptions | +| Microsoft.NetworkCloud/storageAppliances/read | Get properties of the provided storage appliance | +| Microsoft.NetworkCloud/unregister/action | Unregister the subscription for Microsoft.NetworkCloud | +| Microsoft.Resources/deployments/* | Create and manage a deployment | +| Microsoft.Resources/subscriptions/resourceGroups/read | Gets or lists resource groups | ++> [!NOTE] +> In some instances, it may be necessary to assign additional actions to the user. +> One solution would be to create a custom role with the below actions to be assigned to +> the user in conjunction with the Operator Nexus Compute Contributor role. ++#### Ancillary Operator Nexus Compute Contributor Actions ++| Actions | Description | +||| +| Microsoft.OperationalInsights/workspaces/write | Creates a new workspace or links to an existing workspace by providing the customer id from the existing workspace. | +| Microsoft.OperationalInsights/workspaces/read | Gets an existing workspace | +| Microsoft.Resources/subscriptions/resourcegroups/write | Creates or updates a resource group. | ++### Operator Nexus Keyset Administrator Role (Preview) ++Manage interactive access to Azure Operator Nexus Compute resources by adding, removing, +and updating baremetal machine (BMM) and baseboard management (BMC) keysets. | ++| Actions | Description | +|-|-| +| Microsoft.ExtendedLocation/customLocations/deploy/action | Deploy permissions to a Custom Location resource | +| Microsoft.NetworkCloud/clusters/bareMetalMachineKeySets/delete | Delete a bare metal machine key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bareMetalMachineKeySets/read | Get bare metal machine key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bareMetalMachineKeySets/write | Create a new or update an existing bare metal machine key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bmcKeySets/read | Get baseboard management controller key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bmcKeySets/write | Create a new or update an existing baseboard management controller key set of the provided cluster | +| Microsoft.NetworkCloud/clusters/bmcKeySets/delete | Delete a baseboard management controller key set of the provided cluster |