Merge pull request #294924 from MicrosoftDocs/main

2/19/2025 AM Publish

Author: Taojunshen

articles/automation/extension-based-hybrid-runbook-worker-install.md

@@ -77,7 +77,8 @@ If extension-based Hybrid Worker is using custom Hybrid Worker credentials, then
 | Arc-enabled Server | C:\ProgramData\AzureConnectedMachineAgent\Tokens (read) </br> C:\Packages\Plugins\Microsoft.Azure.Automation.HybridWorker.HybridWorkerForWindows (read and execute).
 
 > [!NOTE]
-> When a system has UAC/LUA in place, permissions must be granted directly and not through any group membership. [Learn more](troubleshoot/extension-based-hybrid-runbook-worker.md#scenario-runbooks-go-into-a-suspended-state-on-a-hybrid-runbook-worker-when-using-a-custom-account-on-a-server-with-user-account-control-uac-enabled).
+> - When a system has UAC/LUA in place, permissions must be granted directly and not through any group membership. [Learn more](troubleshoot/extension-based-hybrid-runbook-worker.md#scenario-runbooks-go-into-a-suspended-state-on-a-hybrid-runbook-worker-when-using-a-custom-account-on-a-server-with-user-account-control-uac-enabled).
+> - Due to a current limitation, these folder permissions are removed from the C:\ProgramData\AzureConnectedMachineAgent\Tokens folder on Azure Arc-enabled machines when the Azure Connected Machine agent is updated. The current resolution is to reapply these permissions to the folder. [Learn more](troubleshoot/extension-based-hybrid-runbook-worker.md#scenario-hybrid-runbook-worker-job-execution-on-azure-arc-enabled-windows-server-that-uses-a-custom-credential-is-unexpectedly-suspended).
 
 
 

articles/azure-app-configuration/concept-config-file.md

@@ -19,7 +19,7 @@ The rest of this document discusses both file content profiles in detail and use
 
 ## File content profile: default
 
-The default file content profile in App Configuration tools refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems. App Configuration supports JSON, Yaml, or Properties file formats.
+The default file content profile in App Configuration tools refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems. App Configuration supports JSON, YAML, or Properties file formats.
 
 The following example is a configuration file named `appsettings.json` containing one configuration setting and one feature flag.
 

articles/azure-app-configuration/howto-import-export-data.md

@@ -22,7 +22,7 @@ Import brings configuration data into an App Configuration store from an existin
 
 This guide shows how to import App Configuration data:
 
-- [from a configuration file in Json, Yaml or Properties](#import-data-from-a-configuration-file)
+- [from a configuration file in JSON, YAML or Properties](#import-data-from-a-configuration-file)
 - [from an App Configuration store](#import-data-from-an-app-configuration-store)
 - [from Azure App Service](#import-data-from-azure-app-service)
 
@@ -44,7 +44,7 @@ From the Azure portal, follow these steps:
 
     | Parameter    | Description                                                                             | Example |
     |--------------|-----------------------------------------------------------------------------------------|----------|
-    | File type    | Select the file type for import: YAML, Properties, or JSON. | *Json*   |
+    | File type    | Select the file type for import: YAML, Properties, or JSON. | *JSON*   |
 
 1. Click the **Browse** button, and select the file to import.
 
@@ -53,7 +53,7 @@ From the Azure portal, follow these steps:
 
     | Parameter    | Description                                                                                                                                                                                                                             | Example                   |
     |--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
-    | File content profile    | Select a content profile: Default or KVSet. The *Default* file content profile refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems, supports JSON, Yaml, or Properties file formats. The *KVSet* file content profile refers to a file schema that contains all properties of an App Configuration key-value, including key, value, label, content type, and tags. | *Default*                       |
+    | File content profile    | Select a content profile: Default or KVSet. The *Default* file content profile refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems, supports JSON, YAML, or Properties file formats. The *KVSet* file content profile refers to a file schema that contains all properties of an App Configuration key-value, including key, value, label, content type, and tags. | *Default*                       |
     | Import mode    | The import mode is used to determine whether to ignore identical key-values. With the *Ignore match* option, any key-values in the store that are the same as those in the configuration file are ignored. With the *All* option, all key-values in the configuration file are updated.   | *Ignore match*                       |
     | Exclude feature flag    | If checked, feature flags will not be imported. | *Unchecked*                       |
     | Strict    | If the box is checked, any key-values in the store with the specified prefix and label that are not included in the configuration file are deleted when the File content profile is set to Default. When the File content profile is set to KVSet, any key-values in the store that are not included in the configuration file are deleted. If the box is unchecked, no key-values in the store will be deleted.  | *Unchecked*                       |
@@ -85,7 +85,7 @@ From the Azure CLI, follow the steps below. If you don't have the Azure CLI inst
 
     | Parameter        | Description                                                                                                                                                                                                                                              | Example            |
     |------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
-    | `--separator`    | Optional. The separator is the delimiter for flattening the key-values to Json/Yaml. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;`              |
+    | `--separator`    | Optional. The separator is the delimiter for flattening the key-values to JSON/YAML. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;`              |
     | `--prefix`       | Optional. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of key-values in a configuration store. This prefix will be appended to the front of the "key" property of each imported key-value.                                                               | `TestApp:`         |
     | `--label`        | Optional. Enter a label that will be assigned to your imported key-values.                                                                                                                                                                               | `prod`             |
     | `--content-type` | Optional. Enter `appconfig/kvset` or `application/json` to state that the imported content consists of a Key Vault reference or a JSON file.                                                                                                      | `application/json` |
@@ -265,7 +265,7 @@ Export writes configuration data stored in App Configuration to another destinat
 
 This guide shows how to export App Configuration data:
 
-- [to a configuration file in Json, Yaml or Properties](#export-data-to-a-configuration-file)
+- [to a configuration file in JSON, YAML or Properties](#export-data-to-a-configuration-file)
 - [to an App Configuration store](#export-data-to-an-app-configuration-store)
 - [to an Azure App Service resource](#export-data-to-azure-app-service)
 
@@ -289,7 +289,7 @@ From the [Azure portal](https://portal.azure.com), follow these steps:
     | Parameter          | Description  | Example                  |
     |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
     | File type          | Select the file type for export: YAML, Properties, or JSON. | *JSON*                   | 
-    | File content profile   | Select a content profile: Default or KVSet. The *Default* file content profile refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems, supports JSON, Yaml, or Properties file formats. The *KVSet* file content profile refers to a file schema that contains all properties of an App Configuration key-value, including key, value, label, content type, and tags. | *Default*                   |
+    | File content profile   | Select a content profile: Default or KVSet. The *Default* file content profile refers to the conventional configuration file schema widely adopted by existing programming frameworks or systems, supports JSON, YAML, or Properties file formats. The *KVSet* file content profile refers to a file schema that contains all properties of an App Configuration key-value, including key, value, label, content type, and tags. | *Default*                   |
     | Selection mode          | Select whether to export from regular key-values, which is the default option, or from a snapshot.   | *Default*                   | 
     | Key filter | Used to filter key-values based on the key name for export. If no keys are specified, all keys are eligible.    |      Starts with *TestApp:*              |
     | At a specific time | Optional. Fill out this field to export key-values from a specific point in time in the selected configuration store. If left empty, it defaults to the current point in time of the key-values. | *07/28/2022 12:00:00 AM* |
@@ -323,7 +323,7 @@ From the Azure CLI, follow the steps below. If you don't have the Azure CLI inst
 
     | Parameter        | Description                                                                                                                                                                                                                                             | Example                   |
     |------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
-    | `--separator`    | Optional. The separator is the delimiter for flattening the key-values to Json/Yaml. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;`                     |
+    | `--separator`    | Optional. The separator is the delimiter for flattening the key-values to JSON/YAML. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;`                     |
     | `--prefix`       | Optional. Prefix to be trimmed from each key-value's "key" property. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of key-values in a configuration store. Prefix will be ignored for feature flags.                                                | `TestApp:`                |
 
     Example: export all key-values and feature flags with label "prod" to a JSON file.

articles/azure-netapp-files/TOC.yml

@@ -51,8 +51,16 @@
         href: understand-guidelines-active-directory-domain-service-site.md
       - name: Understand DNS 
         href: domain-name-system-concept.md
-      - name: Understand the use of LDAP
-        href: lightweight-directory-access-protocol.md
+      - name: Understand LDAP
+        items:
+        - name: Understand LDAP basics
+          href: lightweight-directory-access-protocol.md
+        - name: Understand name mapping using LDAP
+          href: lightweight-directory-access-protocol-name-mapping.md
+        - name: Understand the allow local NFS users with LDAP option
+          href: lightweight-directory-access-protocol-local-users.md
+        - name: Understand LDAP schemas
+          href: lightweight-directory-access-protocol-schemas.md
       - name: Understand NFS group memberships and supplemental groups
         href: network-file-system-group-memberships.md
       - name: Understand file locking

articles/azure-netapp-files/azure-netapp-files-configure-export-policy.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.author: anfdocs
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 07/28/2021
+ms.date: 01/28/2025
 ---
 # Configure export policy for NFS or dual-protocol volumes
 
@@ -17,7 +17,7 @@ You can create up to five export policy rules.
 Once created, you can modify details of the export policy rule. The modifiable fields are: 
 
 -	IP address (For example, x.x.x.x)
--	CIDR range (A subnet range; for example, 0.0.0.0/0)
+-	Classless Inter-Domain Routing (CIDR) range (A subnet range; for example, 0.0.0.0/0)
 -	IP address comma separated list (For example, x.x.x.x, y.y.y.y)
 - Access level 
 - [Export policy rule order](network-attached-storage-permissions.md#export-policy-rule-ordering)

articles/azure-netapp-files/azure-netapp-files-create-netapp-account.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/04/2021
+ms.date: 02/04/2025
 ms.author: anfdocs
 ---
 
@@ -19,7 +19,7 @@ You must register your subscription for using the NetApp Resource Provider. For
 
 ## Steps
 
-1. Sign in to the Azure portal.
+1. Log into the Azure portal.
 1. Access the Azure NetApp Files pane by using one of the following methods:
    * Search for **Azure NetApp Files** in the Azure portal search box.
    * Select **All services** in the navigation, and then filter to Azure NetApp Files.

articles/azure-netapp-files/azure-netapp-files-manage-snapshots.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 10/25/2021
+ms.date: 10/25/2024
 ms.author: anfdocs
 ---
 # Create an on-demand snapshot for a volume

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -73,7 +73,7 @@ The following requirements and considerations apply to large volumes. For perfor
 
 ## About 64-bit file IDs
 
-Whereas regular volume use 32-bit file IDs, large volumes employ 64-bit file IDs. File IDs are unique identifiers that allow Azure NetApp Files to keep track of files in the file system. 64-bit IDs are utilized to increase the number of files allowed in a single volume, enabling a large volume able to hold more files than a regular volume. 
+Whereas regular volumes use 32-bit file IDs, large volumes employ 64-bit file IDs. File IDs are unique identifiers that allow Azure NetApp Files to keep track of files in the file system. 64-bit IDs are utilized to increase the number of files allowed in a single volume, enabling a large volume able to hold more files than a regular volume. 
 
 ## Supported regions