Thank you for your feedback! As we work to get Azure Files to parity with Windows File Server, we absolutely agree this functionality is required. For now, I’m leaving this item open so we can collect feedback on it – please vote for it to help us prioritize it!
Will GriesChris Thoms commented
Agree this is a deal breaker for our use of Azure Files in our enterprise, as creating a GPO w/script for each file share is a serious security concern due to exposing the storage account key and the lack of ACL control. Please keep me posted if this feature becomes available.
We recently announce the General Availability of Azure Active Directory Domain Services (Azure AD DS) authentication for Azure Files! By enabling integration with Azure AD DS, you can mount your Azure file share over SMB using Azure AD credentials from Azure AD DS domain joined Windows VMs with NTFS ACLs enforced. For more details, please refer to our blog post:http://aka.ms/azure-file-aadds-authentication-ga-blog.
A part of the GA announcement, we shared the upcoming plan to extend the authentication support to Active Directory (AD) either hosted on-premises or in cloud. If you need an Azure Files solution with AD authentication today, you can consider installing Azure File Sync (AFS) on your Windows File Servers where AD integration is fully supported.
If you are interested to hear future updates on Azure Files Active Directory Authentication, please complete this sign-up survey:https://aka.ms/AzureFilesADAuthPreviewSurvey.
Azure Files TeamChris Thoms supported this idea ·
IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.
Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/
Links to Documentation & Samples
Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc
A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/Chris Thoms commented
in the same situation as Sebastian and Adrian, our iOS app will not be approved unless the backend accepts IPv6 connections. I used the load balancer template to build a QA environment and successfully connected our mobile app via IPv4 and IPv6. While this works, I am in agreement with Chris and Ben that I should be able to associate a AAAA record with a static IPv6 address connected to my VM.