Skip to content

Commit 11690de

Browse files
authored
Merge pull request #298953 from MicrosoftDocs/main
4/28/2025 AM Publish
2 parents d10a66e + e2fca65 commit 11690de

18 files changed

+59
-109
lines changed

articles/azure-netapp-files/configure-unix-permissions-change-ownership-mode.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes | Microsoft Docs
3-
description: Describes how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
2+
title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes
3+
description: Learn how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
44
services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 02/28/2023
8+
ms.date: 04/25/2025
99
ms.author: anfdocs
1010
---
1111
# Configure Unix permissions and change ownership mode for NFS and dual-protocol volumes
@@ -22,31 +22,35 @@ The Unix permissions setting is set to `0770` by default. This default setting g
2222

2323
## Change ownership mode
2424

25-
The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories. You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:
25+
The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories. You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:
2626

2727
* `Restricted` (default) - Only the root user can change the ownership of files and directories.
2828
* `Unrestricted` - Non-root users can change the ownership for files and directories that they own.
2929

3030
## Considerations
3131

3232
* The Unix permissions you specify apply only for the volume mount point (root directory).
33-
* You can modify the Unix permissions on the source volume *but not on the destination volume* that is in a cross-region replication configuration.
33+
* You can modify the Unix permissions on the source volume *but not the destination volume* that is in a replication configuration.
3434

35-
## Steps
35+
## Set Unix permissions for new volumes
3636

3737
1. You can specify the **Unix permissions** and change ownership mode (**`Chown Mode`**) settings under the **Protocol** tab when you [create an NFS volume](azure-netapp-files-create-volumes.md) or [create a dual-protocol volume](create-volumes-dual-protocol.md).
3838

39-
The following example shows the Create a Volume screen for an NFS volume.
39+
The following example shows the Create a volume screen for an NFS volume.
4040

41-
![Screenshots that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
41+
![Screenshot that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
4242

43-
2. For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:
43+
## Set Unix permissions for existing volumes
4444

45-
1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.
46-
![Screenshots that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
45+
For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:
4746

48-
2. To modify the change ownership mode, click the **volume**, click **Export policy**, then modify the **`Chown Mode`** setting.
49-
![Screenshots that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
47+
1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.
48+
49+
![Screenshot that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
50+
51+
2. To modify the change ownership mode, select the **volume**, click **Export policy** then modify the **`Chown Mode`** setting.
52+
53+
![Screenshot that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
5054

5155
## Next steps
5256

articles/azure-resource-manager/templates/template-functions-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 02/12/2025
1010

1111
Resource Manager provides the following functions for getting values related to the current deployment of your Azure Resource Manager template (ARM template):
1212

13-
* [developer](#deployer)
13+
* [deployer](#deployer)
1414
* [deployment](#deployment)
1515
* [environment](#environment)
1616
* [parameters](#parameters)

articles/event-grid/.openpublishing.redirection.event-grid.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "subscribe-to-sap-events.md",
5+
"redirect_url": "/azure/event-grid/partner-events-overview",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "transport-layer-security.md",
510
"redirect_url": "/azure/event-grid/transport-layer-security-configure-minimum-version",

articles/event-grid/partner-events-overview.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,8 +57,6 @@ Through Microsoft Graph API, you can get events from a diverse set of Microsoft
5757
### Auth0
5858
[Auth0](https://auth0.com) is a managed authentication platform for businesses to authenticate, authorize, and secure access for applications, devices, and users. You can create an [Auth0 partner topic](auth0-overview.md) to connect your Auth0 and Azure accounts. This integration allows you to react to, log, and monitor Auth0 events in real time. To try it out, see [Integrate Azure Event Grid with Auth0](auth0-how-to.md).
5959

60-
### SAP
61-
You can configure your SAP system to send events to Azure Event Grid. For more information, see [Subscribe to SAP events](subscribe-to-sap-events.md).
6260

6361
### Tribal Group
6462

articles/event-grid/subscribe-to-partner-events.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,6 @@ Here's the list of partners and a link to submit a request to enable events flow
3535

3636
- [Auth0](auth0-how-to.md)
3737
- [Microsoft Graph API](subscribe-to-graph-api-events.md)
38-
- [SAP](subscribe-to-sap-events.md)
3938
- [Tribal Group](subscribe-to-tribal-group-events.md)
4039

4140

articles/event-grid/subscribe-to-sap-events.md

Lines changed: 0 additions & 51 deletions
This file was deleted.

articles/event-grid/toc.yml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -437,8 +437,6 @@ items:
437437
items:
438438
- name: Auth0
439439
href: auth0-overview.md
440-
- name: SAP
441-
href: subscribe-to-sap-events.md
442440
- name: Tribal Group
443441
href: subscribe-to-tribal-group-events.md
444442
- name: Microsoft Graph API
@@ -560,8 +558,6 @@ items:
560558
href: onboard-partner.md
561559
- name: Subscribe to partner events
562560
href: subscribe-to-partner-events.md
563-
- name: Subscribe to SAP events
564-
href: subscribe-to-sap-events.md
565561
- name: Subscribe to Tribal Group events
566562
href: subscribe-to-tribal-group-events.md
567563
- name: Auth0

articles/event-grid/use-cases.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,6 @@ A multitenant SaaS provider or platform can publish their events to Event Grid t
6666
- [Auth0](auth0-overview.md)
6767
- [Microsoft Graph API](subscribe-to-graph-api-events.md). Through Microsoft Graph API you can get events from [Microsoft Entra ID](microsoft-entra-events.md), [Microsoft Outlook](outlook-events.md), [Teams](teams-events.md), Conversations, security alerts, and Universal Print.
6868
- [Tribal Group](subscribe-to-tribal-group-events.md)
69-
- [SAP](subscribe-to-sap-events.md)
7069

7170
## Pull delivery use cases
7271
Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#push-and-pull-delivery). With this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized using pull delivery.

articles/event-hubs/apache-kafka-streams.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 03/06/2025
88

99
# Kafka Streams for Azure Event Hubs
1010

11-
This article provides details on how to us the [Kafka Streams](https://kafka.apache.org/documentation/streams/) client library with Azure Event Hubs.
11+
This article provides details on how to use the [Kafka Streams](https://kafka.apache.org/documentation/streams/) client library with Azure Event Hubs.
1212

1313
> [!NOTE]
1414
> Kafka Streams functionality is available in **Public Preview** for Event Hubs Premium and Dedicated tiers only.

articles/migrate/toc.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ items:
3232
- name: Appliance requirements
3333
href: migrate-appliance.md
3434
- name: Discover VMware estate
35-
href: tutorial-discover-vmware.md
35+
href: ./vmware/tutorial-discover-vmware.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
3636
- name: Scoped discovery of VMware estate
3737
href: set-discovery-scope.md
3838
- name: Discover Hyper-v estate
@@ -56,7 +56,7 @@ items:
5656
- name: CSV import
5757
href: tutorial-discover-import.md
5858
- name: RVTools import
59-
href: tutorial-import-vmware-using-rvtools-xlsx.md
59+
href: ./vmware/tutorial-import-vmware-using-rvtools-xlsx.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
6060
- name: Create least privileged credentials for SQL discover
6161
href: least-privilege-credentials.md
6262
- name: Explore inventory
@@ -154,13 +154,13 @@ items:
154154
- name: Agent-based migrations
155155
items:
156156
- name: Agent-based migration using portal
157-
href: vmware/tutorial-migrate-vmware-agent.md
157+
href: ./vmware/tutorial-migrate-vmware-agent.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
158158
- name: Agentless migrations
159159
items:
160160
- name: Agentless migrations using portal
161161
href: vmware/tutorial-migrate-vmware.md
162162
- name: Agentless migrations using scripts
163-
href: vmware/tutorial-migrate-vmware-powershell.md
163+
href: ./vmware/tutorial-migrate-vmware-powershell.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
164164
# - name: Limitations
165165
- name: Modernize applications
166166
items:
@@ -185,7 +185,7 @@ items:
185185
- name: Migrate VMware servers
186186
items:
187187
- name: Migrate to Azure Cloud
188-
href: tutorial-migrate-vmware.md
188+
href: ./vmware/tutorial-migrate-vmware.md?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
189189
- name: Migrate to Azure Local
190190
href: /azure/azure-local/migrate/migration-azure-migrate-vmware-overview?toc=/azure/migrate/toc.json&bc=/azure/migrate/breadcrumb/toc.json
191191
- name: Migrate Hyper-V servers

0 commit comments

Comments
 (0)