- #STORAGE FOR MAC AND WINDOWS DOMAIN CODE#
- #STORAGE FOR MAC AND WINDOWS DOMAIN PASSWORD#
- #STORAGE FOR MAC AND WINDOWS DOMAIN MAC#
These basic services become even more important when employees using Macs are highly collaborative creative professionals like designers, publishers, and video editors who perform much more frequent network-based files-related activities than the typical worker, and often on much larger files.
#STORAGE FOR MAC AND WINDOWS DOMAIN MAC#
Once the drive is mapped, make any necessary NTFS ACL Changes as-needed.The presence of Apple Macs in business is growing and IT administrators must take special steps to ensure that Mac users can effectively utilize basic services like network file access, searching, sharing, and printing.Map a drive to your Azure File Share using your AD user account (Windows Explorer, Command-Line, PowerShell, etc.).Note: It is not recommended to keep the drive mapped with the Storage Account Key. This step is necessary so that you are able to successfully map the drive with your user account, as described in step 8. If you used the script from above, you can use the following script to remove the drive mapping as the storage account key. If you used Step 5: Remove Drive Mapping Using Storage account key.If you used Step 5: Set ACL's on File system in Azure Share (.Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port." Write-Error -Message "Unable to reach the Azure storage account via port 445. Net use X: "\\$.net\$AzureFileShare" /user:Azure\ '' $connectTestResult = Test-NetConnection -ComputerName "$.net" -Port 445
#STORAGE FOR MAC AND WINDOWS DOMAIN CODE#
#STORAGE FOR MAC AND WINDOWS DOMAIN PASSWORD#
StorageAccountName $StorageAccountName ` $ResourceGroupName = "My-Resource-Group-Name"
Run "Join-AzStorageAccountForAuth" cmdlet to join Storage account to Azure AD as shown here: Join the Azure Storage Account containing the file share to AD ( ).For our demonstration purposes, this configuration is being used for functionality and convenience. Depending on the security posture needed for a production environment, this configuration would likely have tighter access controls. It is also assumed that you have inserted data into the Azure File Share with a supported tool, like Azure File Sync, AzCopy, Windows Explorer, etc. Knowledge of creating Azure Storage Accounts, Azure File Shares, and Synchronizing on-premise Active Directory user accounts to Azure AD with Azure AD Connect is assumed. The steps to complete this task along with notes on the experience will be listed below. This post is meant to summarize the experience of going through this process and offer some guidance on areas that may be confusing. The process is documented in a multi-part article on Microsoft Docs. The purpose of this post is to walk through the experience of configuring a Windows client to map a drive to an Azure File Share, with the User Experience that they are used to.