@VSHAH804 If you are willing to provision an account for third parties,
So the options I see are:
- SAS to a specific file share
- AD domain join of your Storage Account and give 3rd party an AD account (caution: review if this is really a best-practice for your company as built-in roles like "all domain users" and others can include this account and give unintentded access to 3rd party users)
- You can still use an Azure file share for your day-to-day work and then copy the files you want to share to a blob with AAD auth. ( verify this really works I haven't tried it) The file is likely to lose the metadata like ACLs timestamps and attributes but that might be fine in your scenarios.
I think that would be a good way to round it out.
Additional information: The caution should also apply to a 3rd party account in AAD if their AAD instance is connected to O365
Kindly let us know if the above helps or you need further assistance on this issue.
-----------------------------------------------------------------------------------------------------------------------------------------
Please do not forget to "Accept the answer" wherever the information provided helps you. This will help others in the community as well.