Skip to content

Commit 81f5356

Browse files
Banani-RathBanani-Rath
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 0ef9870 + 6dec090 commit 81f5356

File tree

42 files changed

+446
-83
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+446
-83
lines changed

‎.openpublishing.redirection.json

Lines changed: 150 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41763,6 +41763,156 @@
4176341763
"redirect_url": "/azure/iot-central/core/tutorial-monitor-devices/",
4176441764
"redirect_document_id": true
4176541765
},
41766+
{
41767+
"source_path": "articles/iot-central/core/overview-iot-central-pnp.md",
41768+
"redirect_url": "/azure/iot-central/preview/overview-iot-central/",
41769+
"redirect_document_id": false
41770+
},
41771+
{
41772+
"source_path": "articles/iot-central/core/overview-iot-central-tour-pnp.md",
41773+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-tour/",
41774+
"redirect_document_id": false
41775+
},
41776+
{
41777+
"source_path": "articles/iot-central/core/overview-iot-central-stay-connected-pnp.md",
41778+
"redirect_url": "/azure/iot-central/preview/overview-iot-central-stay-connected/",
41779+
"redirect_document_id": false
41780+
},
41781+
{
41782+
"source_path": "articles/iot-central/core/quick-deploy-iot-central-pnp.md",
41783+
"redirect_url": "/azure/iot-central/preview/quick-deploy-iot-central/",
41784+
"redirect_document_id": false
41785+
},
41786+
{
41787+
"source_path": "articles/iot-central/core/quick-create-pnp-device-pnp.md",
41788+
"redirect_url": "/azure/iot-central/preview/quick-create-pnp-device/",
41789+
"redirect_document_id": false
41790+
},
41791+
{
41792+
"source_path": "articles/iot-central/core/quick-configure-rules-pnp.md",
41793+
"redirect_url": "/azure/iot-central/preview/quick-configure-rules/",
41794+
"redirect_document_id": false
41795+
},
41796+
{
41797+
"source_path": "articles/iot-central/core/quick-monitor-devices-pnp.md",
41798+
"redirect_url": "/azure/iot-central/preview/quick-monitor-devices/",
41799+
"redirect_document_id": false
41800+
},
41801+
{
41802+
"source_path": "articles/iot-central/core/tutorial-define-iot-device-type-pnp.md",
41803+
"redirect_url": "/azure/iot-central/preview/tutorial-define-iot-device-type/",
41804+
"redirect_document_id": false
41805+
},
41806+
{
41807+
"source_path": "articles/iot-central/core/tutorial-connect-pnp-device-pnp.md",
41808+
"redirect_url": "/azure/iot-central/preview/tutorial-connect-pnp-device/",
41809+
"redirect_document_id": false
41810+
},
41811+
{
41812+
"source_path": "articles/iot-central/core/tutorial-define-edge-device-type-pnp.md",
41813+
"redirect_url": "/azure/iot-central/preview/tutorial-define-edge-device-type/",
41814+
"redirect_document_id": false
41815+
},
41816+
{
41817+
"source_path": "articles/iot-central/core/tutorial-use-device-groups-pnp.md",
41818+
"redirect_url": "/azure/iot-central/preview/tutorial-use-device-groups/",
41819+
"redirect_document_id": false
41820+
},
41821+
{
41822+
"source_path": "articles/iot-central/core/tutorial-create-telemetry-rules-pnp.md",
41823+
"redirect_url": "/azure/iot-central/preview/tutorial-create-telemetry-rules/",
41824+
"redirect_document_id": false
41825+
},
41826+
{
41827+
"source_path": "articles/iot-central/core/concepts-architecture-pnp.md",
41828+
"redirect_url": "/azure/iot-central/preview/concepts-architecture/",
41829+
"redirect_document_id": false
41830+
},
41831+
{
41832+
"source_path": "articles/iot-central/core/howto-connect-devkit-pnp.md",
41833+
"redirect_url": "/azure/iot-central/preview/howto-connect-devkit/",
41834+
"redirect_document_id": false
41835+
},
41836+
{
41837+
"source_path": "articles/iot-central/core/howto-connect-ruuvi-pnp.md",
41838+
"redirect_url": "/azure/iot-central/preview/howto-connect-ruuvi/",
41839+
"redirect_document_id": false
41840+
},
41841+
{
41842+
"source_path": "articles/iot-central/core/howto-connect-rigado-cascade-500-pnp.md",
41843+
"redirect_url": "/azure/iot-central/preview/howto-connect-rigado-cascade-500/",
41844+
"redirect_document_id": false
41845+
},
41846+
{
41847+
"source_path": "articles/iot-central/core/howto-monitor-devices-azure-cli-pnp.md",
41848+
"redirect_url": "/azure/iot-central/preview/howto-monitor-devices-azure-cli/",
41849+
"redirect_document_id": false
41850+
},
41851+
{
41852+
"source_path": "articles/iot-central/core/howto-manage-devices-pnp.md",
41853+
"redirect_url": "/azure/iot-central/preview/howto-manage-devices/",
41854+
"redirect_document_id": false
41855+
},
41856+
{
41857+
"source_path": "articles/iot-central/core/howto-create-analytics-pnp.md",
41858+
"redirect_url": "/azure/iot-central/preview/howto-create-analytics/",
41859+
"redirect_document_id": false
41860+
},
41861+
{
41862+
"source_path": "articles/iot-central/core/howto-version-device-template-pnp.md",
41863+
"redirect_url": "/azure/iot-central/preview/howto-version-device-template/",
41864+
"redirect_document_id": false
41865+
},
41866+
{
41867+
"source_path": "articles/iot-central/core/howto-export-data-pnp.md",
41868+
"redirect_url": "/azure/iot-central/preview/howto-export-data/",
41869+
"redirect_document_id": false
41870+
},
41871+
{
41872+
"source_path": "articles/iot-central/core/howto-create-webhooks-pnp.md",
41873+
"redirect_url": "/azure/iot-central/preview/howto-create-webhooks/",
41874+
"redirect_document_id": false
41875+
},
41876+
{
41877+
"source_path": "articles/iot-central/core/howto-use-action-groups-pnp.md",
41878+
"redirect_url": "/azure/iot-central/preview/howto-use-action-groups/",
41879+
"redirect_document_id": false
41880+
},
41881+
{
41882+
"source_path": "articles/iot-central/core/howto-create-custom-rules-pnp.md",
41883+
"redirect_url": "/azure/iot-central/preview/howto-create-custom-rules/",
41884+
"redirect_document_id": false
41885+
},
41886+
{
41887+
"source_path": "articles/iot-central/core/howto-create-custom-analytics-pnp.md",
41888+
"redirect_url": "/azure/iot-central/preview/howto-create-custom-analytics/",
41889+
"redirect_document_id": false
41890+
},
41891+
{
41892+
"source_path": "articles/iot-central/core/howto-administer-pnp.md",
41893+
"redirect_url": "/azure/iot-central/preview/howto-administer/",
41894+
"redirect_document_id": false
41895+
},
41896+
{
41897+
"source_path": "articles/iot-central/core/howto-manage-users-roles-pnp.md",
41898+
"redirect_url": "/azure/iot-central/preview/howto-manage-users-roles/",
41899+
"redirect_document_id": false
41900+
},
41901+
{
41902+
"source_path": "articles/iot-central/core/howto-view-bill-pnp.md",
41903+
"redirect_url": "/azure/iot-central/preview/howto-view-bill/",
41904+
"redirect_document_id": false
41905+
},
41906+
{
41907+
"source_path": "articles/iot-central/core/howto-customize-ui-pnp.md",
41908+
"redirect_url": "/azure/iot-central/preview/howto-customize-ui/",
41909+
"redirect_document_id": false
41910+
},
41911+
{
41912+
"source_path": "articles/iot-central/core/howto-use-app-templates-pnp.md",
41913+
"redirect_url": "/azure/iot-central/preview/howto-use-app-templates/",
41914+
"redirect_document_id": false
41915+
},
4176641916
{
4176741917
"source_path": "articles/iot-central/tutorial-monitor-devices-pnp.md",
4176841918
"redirect_url": "/azure/iot-central/preview/quick-monitor-devices/",

‎articles/active-directory/reports-monitoring/concept-audit-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ This article gives you an overview of the audit report.
3939
## Who can access the data?
4040

4141
* Users in the **Security Administrator**, **Security Reader**, **Report Reader** or **Global Administrator** roles
42-
* In addition, all users (non-administrators) can see their own audit activities
42+
* In addition, all users (non-administrators) can see their own sign-in activities
4343

4444
## Audit logs
4545

‎articles/app-service/configure-ssl-certificate.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,10 @@ The free App Service Managed Certificate is a turn-key solution for securing you
6464
- Does not support naked domains.
6565
- Is not exportable.
6666

67+
> [!NOTE]
68+
> The free certificate is issued by DigiCert. For some top-level domains, you must explicitly allow DigiCert as a certificate issuer by creating a [CAA domain record](https://wikipedia.org/wiki/DNS_Certification_Authority_Authorization) with the value: `0 issue digicert.com`.
69+
>
70+
6771
To create a free App Service Managed Certificate:
6872

6973
In the <a href="https://portal.azure.com" target="_blank">Azure portal</a>, from the left menu, select **App Services** > **\<app-name>**.

‎articles/azure-netapp-files/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,12 @@
4747
href: azure-netapp-files-set-up-capacity-pool.md
4848
- name: Delegate a subnet to Azure NetApp Files
4949
href: azure-netapp-files-delegate-subnet.md
50-
- name: Create an NFS volume for Azure NetApp Files
51-
href: azure-netapp-files-create-volumes.md
5250
- name: Create an SMB volume for Azure NetApp Files
5351
href: azure-netapp-files-create-volumes-smb.md
52+
- name: Create an NFS volume for Azure NetApp Files
53+
href: azure-netapp-files-create-volumes.md
54+
- name: Configure NFSv4.1 default domain for Azure NetApp Files
55+
href: azure-netapp-files-configure-nfsv41-domain.md
5456
- name: Configure export policy for an NFS volume
5557
href: azure-netapp-files-configure-export-policy.md
5658
- name: Manage volumes

‎articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: Configure NFSv4.1 default domain for Azure NetApp Files | Microsoft Docs
3+
description: Describes how to configure the NFS client for using NFSv4.1 with Azure NetApp Files.
4+
documentationcenter: ''
5+
author: b-juche
6+
manager: ''
7+
editor: ''
8+
9+
ms.assetid:
10+
ms.service: azure-netapp-files
11+
ms.workload: storage
12+
ms.tgt_pltfrm: na
13+
ms.devlang: na
14+
ms.topic: conceptual
15+
ms.date: 11/08/2019
16+
ms.author: b-juche
17+
---
18+
# Configure NFSv4.1 default domain for Azure NetApp Files
19+
20+
NFSv4 introduces the concept of an authentication domain. Azure NetApp Files currently supports root-only user mapping from the service to the NFS client. To use the NFSv4.1 functionality with Azure NetApp Files, you need to update the NFS client.
21+
22+
## Default behavior of user/group mapping
23+
24+
Root mapping defaults to the `nobody` user because the NFSv4 domain is set to `localdomain`. When you mount an Azure NetApp Files NFSv4.1 volume as root, you will see file permissions as follows:
25+
26+
![Default behavior of user/group mapping for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-default-behavior-user-group-mapping.png)
27+
28+
As the above example shows, the user for `file1` should be `root`, but it maps to `nobody` by default. This article shows you how to set the `file1` user to `root`.
29+
30+
## Steps
31+
32+
1. Edit the `/etc/idmapd.conf` file on the NFS client.
33+
Uncomment the line `#Domain` (that is, remove the `#` from the line), and change the value `localdomain` to `defaultv4iddomain.com`.
34+
35+
Initial configuration:
36+
37+
![Initial configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-initial-config.png)
38+
39+
Updated configuration:
40+
41+
![Updated configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-updated-config.png)
42+
43+
2. Unmount any currently mounted NFS volumes.
44+
3. Update the `/etc/idmapd.conf` file.
45+
4. Restart the `rpcbind` service on your host (`service rpcbind restart`), or simply reboot the host.
46+
5. Mount the NFS volumes as required.
47+
48+
See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
49+
50+
The following example shows the resulting user/group change:
51+
52+
![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-resulting-config.png)
53+
54+
As the example shows, the user/group has now changed from `nobody` to `root`.
55+
56+
## Behavior of other (non-root) users and groups
57+
58+
Azure NetApp Files supports local users (users created locally on a host) who have permissions associated with files or folders in NFSv4.1 volumes. However, the service does not currently support mapping the users/groups across multiple nodes. Therefore, users created on one host do not map by default to users created on another host.
59+
60+
In the following example, `Host1` has three existing test user accounts (`testuser01`, `testuser02`, `testuser03`):
61+
62+
![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-host1-users.png)
63+
64+
On `Host2`, note that the test user accounts have not been created, but the same volume is mounted on both hosts:
65+
66+
![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-host2-users.png)
67+
68+
## Next step
69+
70+
[Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
71+

‎articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 10/12/2019
16+
ms.date: 11/08/2019
1717
ms.author: b-juche
1818
---
1919
# Create an NFS volume for Azure NetApp Files
@@ -38,7 +38,7 @@ A subnet must be delegated to Azure NetApp Files.
3838
Support for UNIX mode bits (read, write, and execute) is available for NFSv3 and NFSv4.1. Root-level access is required on the NFS client to mount NFS volumes.
3939

4040
* Local user/group and LDAP support for NFSv4.1
41-
Currently, NFSv4.1 supports root access to volumes only.
41+
Currently, NFSv4.1 supports root access to volumes only. See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md).
4242

4343
## Best practice
4444

@@ -110,6 +110,7 @@ A subnet must be delegated to Azure NetApp Files.
110110

111111
## Next steps
112112

113+
* [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md)
113114
* [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
114115
* [Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md)
115116
* [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)

‎articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 03/07/2019
16+
ms.date: 11/08/2019
1717
ms.author: b-juche
1818
---
1919
# Mount or unmount a volume for Windows or Linux virtual machines
@@ -27,5 +27,8 @@ You can mount or unmount a volume for Windows or Linux virtual machines as neces
2727

2828
![Mount instructions SMB](../media/azure-netapp-files/azure-netapp-files-mount-instructions-smb.png)
2929

30-
If you are using NFSv4.1, use the following command to mount your file system:
31-
`sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT`
30+
If you are using NFSv4.1, use the following command to mount your file system:
31+
32+
`sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT`
33+
34+
See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md).

‎articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 08/26/2019
16+
ms.date: 11/08/2019
1717
ms.author: b-juche
1818
---
1919
# Solution architectures using Azure NetApp Files
@@ -34,6 +34,7 @@ This article provides references to best practices that can help you understand
3434
* [High availability for SAP NetWeaver on Azure VMs on SUSE Linux Enterprise Server with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-netapp-files)
3535
* [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-rhel-netapp-files)
3636
* [SAP HANA scale-out with standby node on Azure VMs with Azure NetApp Files on SUSE Linux Enterprise Server](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse)
37+
* [SAP HANA Azure virtual machine storage configurations](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-vm-operations-storage)
3738

3839
## Talon solutions
3940

‎articles/data-factory/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -616,6 +616,8 @@
616616
href: connector-troubleshoot-guide.md
617617
- name: Troubleshooting Azure-SSIS IR Management
618618
href: ssis-integration-runtime-management-troubleshoot.md
619+
- name: Troubleshooting Self-hosted IR
620+
href: self-hosted-integration-runtime-troubleshoot-guide.md
619621
- name: Troubleshooting Package Execution in Azure-SSIS IR
620622
href: ssis-integration-runtime-ssis-activity-faq.md
621623
- name: Troubleshooting Data Flows

‎articles/data-factory/media/self-hosted-integration-runtime-troubleshoot-guide/command-line-error.png

96.2 KB
Loading

0 commit comments

Comments
 (0)