Accessing Workgroup from Azure File Server

Question

Accessing Workgroup from Azure File Server

Sriram S 0

Need support regarding an issue with accessing our workgroup from an Azure File Server. We are currently unable to access shared folders or resources on the workgroup machines from the Azure server.

Sriram S 0 Reputation points

2025-11-26T10:42:00.8833333+00:00
Dear Ravi,

Thank you for your response.

Please find the answers to your queries below:

Could you please confirm if the Azure File Share is private or public?

The Azure File Share is created on our Azure server and is accessible only to domain-joined devices. It is private and restricted within our environment.

Could you please confirm how you are accessing the file share—through Entra ID or SAS token?

We are accessing the file share using Entra ID authentication, and the configuration has been verified from our end.

What error message are you getting while accessing the Azure File Share?

Workgroup machines receive a login prompt, but the authentication fails even after entering valid credentials. No specific error code is shown - only repeated credential prompts.

Are you able to access the Azure File Share from other machines or VMs?

Yes, domain-joined devices can access the Azure File Share without issues. Only non-domain (workgroup) machines are unable to authenticate and access the share.

Kindly support us on this and let me know if you need any further details from my side.
Ravi Varma Mudduluru 3,550 Reputation points Microsoft External Staff Moderator

2025-11-27T09:22:33.5533333+00:00

Hello @Sriram S,

Thank you for sharing the details.

From your message, I understand that you are experiencing issues with the workgroup machine, but you can log in on the domain-joined machine. This suggests that the Azure file share is not causing the problem.

If the issue is specific to one machine, please check with your local IT team. Alternatively, if you are trying to access the file share using Entra ID credentials, try using SAS token authentication on the affected machine instead.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Sriram S 0 Reputation points

2025-11-27T09:53:31.46+00:00

Thank you for your response.

Currently, access is working on domain-joined machines, but non-domain devices are unable to connect. Could you please share the detailed steps or configuration requirements to enable Windows/Entra ID–based authentication for users on non-domain devices?

If this scenario is not supported, kindly suggest the recommended alternative.

Looking forward to your guidance.
Ravi Varma Mudduluru 3,550 Reputation points Microsoft External Staff Moderator

2025-11-27T18:11:01.2733333+00:00

Hello @Sriram S,

Could you please share us the below requested details to understand the issue deeper?

Could you please confirm the Azure file share is in private or public?

Could you please confirm how you are accessing the file share through Entra ID or SAS token?

What error message are you getting while access the Azure file share?

Are you able to access the Azure File Share from other machines or VMs?

2 answers

Your answer

Sriram S 0 Reputation points

2025-11-26T10:42:00.8833333+00:00

Dear Ravi,

Thank you for your response.

Please find the answers to your queries below:

Could you please confirm if the Azure File Share is private or public?

The Azure File Share is created on our Azure server and is accessible only to domain-joined devices. It is private and restricted within our environment.

Could you please confirm how you are accessing the file share—through Entra ID or SAS token?

We are accessing the file share using Entra ID authentication, and the configuration has been verified from our end.

What error message are you getting while accessing the Azure File Share?

Workgroup machines receive a login prompt, but the authentication fails even after entering valid credentials. No specific error code is shown - only repeated credential prompts.

Are you able to access the Azure File Share from other machines or VMs?

Yes, domain-joined devices can access the Azure File Share without issues. Only non-domain (workgroup) machines are unable to authenticate and access the share.

Kindly support us on this and let me know if you need any further details from my side.
Ravi Varma Mudduluru 3,550 Reputation points Microsoft External Staff Moderator

2025-11-27T09:22:33.5533333+00:00

Hello @Sriram S,

Thank you for sharing the details.

From your message, I understand that you are experiencing issues with the workgroup machine, but you can log in on the domain-joined machine. This suggests that the Azure file share is not causing the problem.

If the issue is specific to one machine, please check with your local IT team. Alternatively, if you are trying to access the file share using Entra ID credentials, try using SAS token authentication on the affected machine instead.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Sriram S 0 Reputation points

2025-11-27T09:53:31.46+00:00

Thank you for your response.

Currently, access is working on domain-joined machines, but non-domain devices are unable to connect. Could you please share the detailed steps or configuration requirements to enable Windows/Entra ID–based authentication for users on non-domain devices?

If this scenario is not supported, kindly suggest the recommended alternative.

Looking forward to your guidance.
Ravi Varma Mudduluru 3,550 Reputation points Microsoft External Staff Moderator

2025-11-27T18:11:01.2733333+00:00

Hello @Sriram S,

Could you please share us the below requested details to understand the issue deeper?

Could you please confirm the Azure file share is in private or public?

Could you please confirm how you are accessing the file share through Entra ID or SAS token?

What error message are you getting while access the Azure file share?

Are you able to access the Azure File Share from other machines or VMs?

Answer 1

Hello @Sriram S,

Thanks for reaching Microsoft Q&A.

From the above comment, you are able to access the file server on domain-joined machines, but non-domain devices are unable to connect.

If the machine is not in domain, it is not possible to login with Entra ID authentication.

The alternate approach is to connect Azure file share from the workgroup machine using Access key. please follow the below steps

Step 1: User's image

Step: 2 User's image

Step:3 - Please copy the above script and run it in your local PowerShell and the file share will add to your local machine

User's image

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 2

To access shared folders or resources on workgroup machines from an Azure File Server, you may need to ensure that the appropriate network configurations and permissions are in place. Here are some steps to consider:

Network Configuration: Ensure that your Azure File Server can communicate with the workgroup machines. This may involve configuring your firewall settings to allow traffic between the Azure environment and the on-premises network.
Authentication: Azure Files supports NTLMv2 authentication. Ensure that your workgroup machines are configured to use NTLMv2, as NTLMv1 is not supported and can lead to connectivity issues.
Access Permissions: Verify that the user accounts being used to access the shared folders have the necessary permissions on both the Azure File Server and the workgroup machines.
DNS Resolution: Ensure that the Azure File Server can resolve the names of the workgroup machines. You may need to configure DNS settings or use IP addresses directly.
Testing Connectivity: Use tools like Test-NetConnection to verify that the Azure File Server can reach the workgroup machines on the necessary ports (e.g., SMB over port 445).

If issues persist, consider reviewing network traces to identify any potential blocks or misconfigurations in the connection process.

References:

Share via

Accessing Workgroup from Azure File Server

2 answers

Your answer