Merge pull request #314938 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-20 17:00 UTC

Author: learn-build-service-prod[bot]

CODEOWNERS

@@ -38,3 +38,6 @@
 /articles/container-registry @jasonwhowell @thomps23
 /articles/kubernetes-fleet @MicrosoftDocs/azure-docs-codeowners
 /articles/reliability @thomps23
+/articles/sentinel @thomps23
+/articles/defender-for-iot @thomps23
+/articles/external-attack-surface-management @thomps23

articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Create Bicep files - Visual Studio
 description: Use Visual Studio and the Bicep extension to create Bicep files for deploy Azure resources.
-ms.date: 12/22/2025
+ms.date: 01/13/2026
 ms.topic: quickstart
 ms.custom: devx-track-bicep
 #Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio to create and edit Bicep files, so I can use them to deploy Azure resources.
@@ -20,6 +20,18 @@ Similar authoring experience is also supported in Visual Studio Code. See [Quick
 - Visual Studio Bicep extension. See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 - Bicep file deployment requires either the latest [Azure CLI](/cli/azure/) or the latest [Azure PowerShell module](/powershell/azure/new-azureps-module-az).
 
+> [!NOTE]
+> To make all diagnostics generated by Bicep (Errors, Warnings, and Informational messages) are correctly surfaced as native MSBuild diagnostics, configure `BicepTreatInfoAsWarnings` in your project file. For example:
+>
+> ```xml
+> <Project Sdk="Microsoft.Build.NoTargets">
+>   <PropertyGroup>
+>     <TargetFramework>net472</TargetFramework>
+>     <BicepTreatInfoAsWarnings>true</BicepTreatInfoAsWarnings>
+>   </PropertyGroup>
+> </Project>
+> ```
+
 ## Add resource snippet
 
 Launch Visual Studio and create a new file named **main.bicep**.

articles/cost-management-billing/manage/direct-ea-azure-usage-charges-invoices.md

@@ -3,7 +3,7 @@ title: View your Azure usage summary details and download reports for EA enrollm
 description: This article explains how enterprise administrators of direct and indirect Enterprise Agreement (EA) enrollments can view a summary of their usage data, Azure Prepayment consumed, and charges associated with other usage in the Azure portal.
 author: SandeepReddyAcc
 ms.author: v-salin
-ms.date: 09/22/2025
+ms.date: 04/20/2026
 ms.topic: how-to
 ms.service: cost-management-billing
 ms.subservice: enterprise

articles/cost-management-billing/manage/direct-ea-billing-invoice-documents.md

@@ -6,7 +6,7 @@ ms.reviewer: v-salin
 ms.service: cost-management-billing
 ms.subservice: enterprise
 ms.topic: reference
-ms.date: 09/23/2025
+ms.date: 04/20/2026
 ms.author: v-salin
 ---
 

articles/cost-management-billing/manage/ea-azure-marketplace.md

@@ -6,7 +6,7 @@ ms.reviewer: v-salin
 ms.service: cost-management-billing
 ms.subservice: enterprise
 ms.topic: how-to
-ms.date: 09/23/2025
+ms.date: 04/20/2026
 ms.author: v-salin
 ---
 

articles/cost-management-billing/manage/ea-billing-administration-partners.md

@@ -3,7 +3,7 @@ title: EA billing administration for partners in the Azure portal
 description: This article explains the common tasks that a partner administrator accomplishes in the Azure portal to manage indirect enterprise agreements.
 author: SandeepReddyAcc
 ms.author: v-salin
-ms.date: 09/24/2025
+ms.date: 04/20/2026
 ms.topic: how-to
 ms.service: cost-management-billing
 ms.subservice: enterprise

articles/storage/files/files-managed-identities.md

@@ -1,24 +1,24 @@
 ---
-title: Use Managed Identities with Azure Files (Preview)
-description: Learn how to authenticate managed identities to allow applications and VMs to access SMB Azure file shares by using identity-based authentication with Entra ID.
+title: Use Managed Identities with Azure Files
+description: Learn how to authenticate managed identities to allow applications and VMs to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID.
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: how-to
-ms.date: 03/27/2026
+ms.date: 04/20/2026
 ms.author: kendownie
 ms.custom:
   - devx-track-azurepowershell
 zone_pivot_groups: azure-files-windows-linux
 # Customer intent: As a cloud administrator, I want to improve security by authenticating managed identities to allow applications and virtual machines to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID instead of using a storage account key.
 ---
 
-# Access SMB Azure file shares by using managed identities with Microsoft Entra ID (preview)
+# Access SMB Azure file shares by using managed identities with Microsoft Entra ID
 
 **Applies to:** :heavy_check_mark: SMB file shares
 
-This article explains how you can use [managed identities](/entra/identity/managed-identities-azure-resources/overview) to allow Windows and Linux virtual machines (VMs) to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID (preview).
+This article explains how you can use [managed identities](/entra/identity/managed-identities-azure-resources/overview) to allow Windows and Linux virtual machines (VMs) to access SMB Azure file shares by using identity-based authentication with Microsoft Entra ID.
 
-A managed identity is an identity in Entra ID that Azure automatically manages. Typically, you use managed identities when developing cloud applications to manage the credentials for authenticating to Azure services.
+A managed identity is an identity in Microsoft Entra ID that Azure automatically manages. Typically, you use managed identities when developing cloud applications to manage the credentials for authenticating to Azure services. Azure Files now supports both application managed identities and end‑user identity-based access on the same storage account. Applications and users are independently authenticated via Microsoft Entra ID and authorized through a shared permissions model.
 
 By the end of this guide, you create a storage account that's ready to access with a managed identity. You also learn how to create a managed identity for a VM and generate an OAuth token for it. Then you mount a file share by using managed identity-based authentication and authorization. Using a managed identity eliminates the need to use a storage account key.
 
@@ -34,7 +34,7 @@ Benefits include:
 
 - **Fine-grained access control**: Role-based access at the identity level.
 
-- **Automation friendly**: Easy to integrate with continuous integration and continuous delivery (CI/CD) pipelines, Azure Kubernetes Service (AKS) workloads, and customer applications.
+- **Automation friendly**: Easy to integrate with continuous integration and continuous delivery (CI/CD) pipelines, [Azure Kubernetes Service (AKS)](/azure/aks/create-volume-azure-files#use-managed-identity-to-access-azure-files-storage-preview) workloads, and customer applications.
 
 - **Cost effective**: No extra storage cost for managed identities.
 
@@ -56,7 +56,7 @@ The clients that need to authenticate by using a managed identity shouldn't be j
 
 ## Configure the managed identity's access property on your storage account
 
-To authenticate a managed identity, you must enable the `SMBOAuth` property on the storage account that contains the Azure file share you want to access. We recommend creating a new storage account for this purpose. You can use an existing storage account only if it doesn't have any other identity source configured.
+To authenticate a managed identity, you must enable the `SMBOAuth` property on the storage account that contains the Azure file share you want to access. We recommend creating a new storage account for this purpose, although you can use an existing storage account.
 
 To enable the `SMBOAuth` property on your storage account, use either the Azure portal or Azure PowerShell. For instructions, select the appropriate tab.
 
@@ -66,7 +66,7 @@ To create a new storage account with the `SMBOAuth` property enabled by using th
 
 :::image type="content" source="media/managed-identities/enable-managed-identity.png" alt-text="Screenshot that shows how to enable a managed identity for SMB when creating a new storage account by using the Azure portal." border="true":::
 
-Alternatively, you can enable the `SMBOAuth` property on an existing storage account, as long as the storage account doesn't have any other identity source configured.
+Alternatively, you can enable the `SMBOAuth` property on an existing storage account.
 
 Go to the storage account. On the service menu, under **Settings**, select **Configuration**. Under **Managed Identity for SMB**, select **Enabled**, and then select **Save**.