Merge pull request #297736 from MicrosoftDocs/main

4/7/2025 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -6740,7 +6740,7 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/work-with-styx-objects-and-indicators.md",
+      "source_path": "articles/sentinel/work-with-styx-objects-and-indicators.md",
       "redirect_url": "/azure/sentinel/work-with-styx-objects-indicators",
       "redirect_document_id": false
     },

articles/app-service/tutorial-sidecar-local-small-language-model.md

@@ -75,6 +75,7 @@ This section assumes that you already built a Phi-3 Docker image and uploaded it
     - **Image type**: **Public**
     - **Registry server URL**: *mcr.microsoft.com*
     - **Image and tag**: *appsvc/docs/sidecars/sample-experiment:phi3-python-1.0*
+    - **Port**: *8000*
 1. Select **Apply**.
 
 ## 4. Verify the running app
@@ -144,4 +145,4 @@ To upload the built image to Azure Container Registry, see [Push your first imag
 
 ## More resources
 
-- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)
+- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)

articles/azure-app-configuration/feature-management-javascript-reference.md

@@ -130,6 +130,35 @@ const featureProvider = new ConfigurationMapFeatureFlagProvider(appConfig);
 const featureManager = new FeatureManager(featureProvider);
 ```
 
+#### Use Azure App Configuration to dynamically control the state of the feature flag
+
+Azure App Configuration is not only a solution to externalize storage and centralized management of your feature flags, but also it allows to dynamically turn on/off the feature flags.
+
+To enable the dynamic refresh for feature flags, you need to configure the `refresh` property of `featureFlagOptions` when loading feature flags from Azure App Configuration.
+
+``` typescript
+const appConfig = await load("YOUR_APP-CONFIG-ENDPOINT",  new DefaultAzureCredential(),  { 
+    featureFlagOptions: { 
+        enabled: true,
+        refresh: {
+            enabled: true, // enable the dynamic refresh for feature flags
+            refreshIntervalInMs: 30_000
+        }
+    } 
+});
+
+const featureProvider = new ConfigurationMapFeatureFlagProvider(appConfig);
+const featureManager = new FeatureManager(featureProvider);
+```
+
+You need to call the `refresh` method to get the latest feature flag state.
+
+```typescript
+await appConfig.refresh(); // Refresh to get the latest feature flags
+const isBetaEnabled = await featureManager.isEnabled("Beta");
+console.log(`Beta is enabled: ${isBetaEnabled}`);
+```
+
 > [!NOTE]
 > For more information about how to use feature management library with Azure App Configuration, please go to the [quickstart](./quickstart-javascript.md).
 

articles/azure-maps/power-bi-visual-get-started.md

@@ -159,7 +159,7 @@ The Azure Maps Power BI visual is available in the following services and applic
 | Power BI export                          | No           |
 | Power BI subscriptions                   | No           |
 
-**Where is Azure Maps available?**
+**Where is Azure Maps Visual for Power BI available?**
 
 At this time, Azure Maps is currently available in all countries and regions except:
 

articles/azure-netapp-files/backup-restore-new-volume.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/17/2023
+ms.date: 04/07/2025
 ms.author: anfdocs
 ---
 # Restore a backup to a new volume
@@ -14,27 +14,27 @@ Restoring a backup creates a new volume with the same protocol type. This articl
 
 ## Considerations
 
-* You can restore backups only within the same NetApp account. Restoring backups across NetApp accounts are not supported. 
+* You can restore backups only within the same NetApp account. Restoring backups across NetApp accounts isn't supported. 
 
 * You can restore backups to a different capacity pool within the same NetApp account.
 
-* You can restore a backup only to a new volume. You cannot overwrite the existing volume with the backup. 
+* You can restore a backup only to a new volume. You can't overwrite the existing volume with the backup. 
 
-* The new volume created by the restore operation cannot be mounted until the restore completes. 
+* The new volume created by the restore operation can't be mounted until the restore completes. 
 
 * You should trigger the restore operation when there are no baseline backups. Otherwise, the restore might increase the load on the Azure Blob account where your data is backed up. 
 
 * For volumes greater than 10 TiB, it can take multiple hours to transfer all the data from the backup media.
 
-* Restoring a backup to a new volume is not dependent on the networking type used by the source volume. You can restore the backup of a volume configured with Basic networking to a volume configured with Standard networking and vice versa.
+* Restoring a backup to a new volume isn't dependent on the networking type used by the source volume. You can restore the backup of a volume configured with Basic networking to a volume configured with Standard networking and vice versa.
 
 * In the Volume overview page, refer to the **Originated from** field to see the name of the snapshot used to create the volume. 
 
 * See [Restoring volume backups from vaulted snapshots](snapshots-introduction.md#restoring-volume-backups-from-vaulted-snapshots) for more information. 
 
 
 > [!IMPORTANT]
-> Running multiple concurrent volume restores using Azure NetApp Files backup may increase the time it takes for each individual, in-progress restore to complete. As such, if time is a factor to you, you should prioritize and sequentialize the most important volume restores and wait until the restores are complete before starting another, lower priority, volume restores.  
+> Running multiple concurrent volume restores using Azure NetApp Files backup may increase the time it takes for each individual, in-progress restore to complete. I time is a factor, prioritize and sequentialize the most important volume restores and wait until the restores are complete before starting other, lower priority volume restores.  
 
 See [Requirements and considerations for Azure NetApp Files backup](backup-requirements-considerations.md) for more considerations about using Azure NetApp Files backup. See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md) for information about minimums and maximums. 
 

articles/azure-netapp-files/manage-file-access-logs.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 04/04/2025
+ms.date: 04/07/2025
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -24,7 +24,7 @@ File access logs provide file access logging for individual volumes, capturing f
 * File access logs occasionally create duplicate log entries that must be filtered manually. 
 * Deleting any diagnostic settings configured for `ANFFileAccess` causes any file access logs for any volume with that setting to become disabled. See the [diagnostic setting configuration](#diagnostic) for more information. 
 * Before enabling file access logs on a volume, either [access control lists (ACLs)](configure-access-control-lists.md) or Audit access control entries (ACEs) need to be set on a file or directory. You must set ACLs or Audit ACEs after mounting a volume.  
-* File access logs provide no explicit or implicit expectations or guarantees around logging for auditing and compliance purposes. 
+* Azure NetApp Files file access logs provide detailed information about successful and failed requests to the storage service. This information can be used to monitor individual requests and to diagnose file access issues. Requests are logged on a best-effort basis, meaning that most requests result in a log record, but the completeness and timeliness of file access logs aren't guaranteed. The Azure NetApp Files file access logs feature doesn't provide explicit or implicit expectations or guarantees around logging for auditing and compliance purposes.  
 
 ### Performance considerations 
 

articles/azure-resource-manager/templates/deployment-modes.md

@@ -23,7 +23,7 @@ In incremental mode, Resource Manager **leaves unchanged** resources that exist
 
 > [!IMPORTANT]
 >
-> Incremental mode is the recommended deployment dode. If there is a need to delete resources as part of a Bicep file or ARM JSON template, use [deployment stacks](../bicep/deployment-stacks.md).
+> Incremental mode is the recommended deployment mode. If there is a need to delete resources as part of a Bicep file or ARM JSON template, use [deployment stacks](../bicep/deployment-stacks.md).
 >
 > When redeploying an existing resource in incremental mode, all properties are reapplied. The **properties aren't incrementally added**. A common misunderstanding is to think properties that aren't specified in the template are left unchanged. If you don't specify certain properties, Resource Manager interprets the deployment as overwriting those values. Properties that aren't included in the template are reset to the default values. Specify all non-default values for the resource, not just the ones you're updating. The resource definition in the template always contains the final state of the resource. It can't represent a partial update to an existing resource.
 

articles/azure-vmware/deploy-disaster-recovery-using-jetstream.md

@@ -324,7 +324,7 @@ This cmdlet disables JetStream DR only on one of the clusters and doesn't comple
 
 JetStream DR is a solution that [JetStream Software](https://www.jetstreamsoft.com/) supports. For any product or support issues with JetStream, contact [email protected].  
 
-Azure VMware Solution uses the Run command to automate both the install and uninstall of JetStream DR. Contact Microsoft support for any issue with the run commands. For issues with JetStream install and uninstall cmdlets, contact JetStream for support. 
+Azure VMware Solution uses the Run command to automate both the install and uninstall of JetStream DR. Contact Microsoft support for any issue with the run commands. For issues with JetStream install and uninstall cmdlets, contact JetStream for [support](https://jetstreamsoft.com/portal/online-docs/contactJS/ContactJetStreamSoftware.html). 
 
 
 

articles/bastion/native-client.md

@@ -5,7 +5,7 @@ description: Learn how to configure Bastion for native client connections.
 author: cherylmc
 ms.service: azure-bastion
 ms.topic: how-to
-ms.date: 01/28/2025
+ms.date: 04/07/2025
 ms.author: cherylmc
 ---
 
@@ -15,7 +15,7 @@ This article helps you configure your Bastion deployment to accept connections f
 
 :::image type="content" source="./media/native-client/native-client-architecture.png" alt-text="Diagram shows a connection via native client." lightbox="./media/native-client/native-client-architecture.png":::
 
-You can configure this feature by modifying an existing Bastion deployment, or you can deploy Bastion with the feature configuration already specified. Your capabilities on the VM when connecting via native client are dependent on what is enabled on the native client.
+You can configure this feature by modifying an existing Bastion deployment, or you can deploy Bastion with the feature configuration already specified. Your capabilities on the VM when connecting via native client are dependent on what is enabled on the native client. Keep in mind that at this time, [session recording](session-recording.md) isn't available for native client.
 
 > [!NOTE]
 > [!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]

articles/communication-services/concepts/analytics/logs/call-summary-log-schema.md

@@ -74,6 +74,7 @@ This table describes each property.
 | `ParticipantEndSubCode`| Represents the Calling SDK error subcode that the SDK emits (when relevant) for each `participantId` value. | 
 | `ResultCategory`| Represents the category of the participant ending the call. It can be one of these four values: Success, ExpectedError, UnexpectedClientError, UnexpectedServerError. |
 | `DiagnosticOptions`| This value allows developers to attach custom tags to their client telemetry, which can then be viewed in the Call Diagnostics section. This helps in identifying and troubleshooting issues more effectively. To learn how to add custom tags to this value, refer to [Tutorial on adding custom tags to your client telemetry](../../../tutorials/voice-video-calling/diagnostic-options-tag.md) |
+| `callDebuggingInfo`| This value contains json object with key-value pairs that represent internal properties of the call used for Microsoft debugging purposes.|
 
 ### Error codes 
 
@@ -336,4 +337,4 @@ If you have multiple Azure Communications Services resource IDs, you must enable
 - Learn about the [insights dashboard to monitor Voice Calling and Video Calling logs](/azure/communication-services/concepts/analytics/insights/voice-and-video-insights).
 
 - Learn how to use call logs to diagnose call quality and reliability
-  issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)
+  issues with Call Diagnostics, see: [Call Diagnostics](../../voice-video-calling/call-diagnostics.md)