Skip to main content

Migrating File Server (Share) to Azure

Let’s take a look on what are the current solution on Azure when we want to migrate our local file storage from on-premises to cloud.

Context
On the current system, let us imagine that we have Windows File Server that it is used to share filers inside the company. The File Server is fully integrated with our Active Directory server and based on roles we allow/restrict access to different folders/files.


What we want to do?
We want to migrate to Azure this solution in such a way that we don’t need to manage the File Server machines and also to be able to have control on file sharing permissions using user roles (Active Directory integration).
Addition to this, we want to be able to attach as a shared folder or partition the shared content on the client machine.

Azure Files
An extremely powerful solution provided by Microsoft, which allow us to store our files in Azure and share them with others. The SMB protocol is fully supported, meaning that we can attach the shared on our client machines as a shared folder.
It is the right thing that we need, expect one small thing – NO integration with Active Directory. It means that to be able to attach a share folder or access content we will need to use the storage account name and account key. This will never work in an organization with 10.000 people where you want to control and manage use access, as you would do inside a File Server.

SharePoint on Azure
This nice solution would work. The problem with it is the extra complexity that SharePoint would add for the IT team. In the end they only want to allow file sharing capabilities, they don’t want to manage this things inside SharePoint.
There are companies that might access this solution, but depends from one organization to another.

OneDrive for Business
It’s a great tool that can be used for file sharing inside the team or from one person to a group. But it’s not seen as a mainstream tool that can be used for file sharing inside the company. Even if there is support to share a folder/file to an AD group, it is still a basic tool, that would not as we expected if we would need to share content to 10.000 people.
Works great for small organizations or for a team inside a company.

Migrate File Server machines to Azure
This involves taking the current file storage solution that you have on-premises and put it on top of Azure VMs. The files can be pushed directly to Azure Files and mapped as shared folders inside the File Server VMs. Based on user roles, the File Server would be cable to fetch content, as they would do on-premises.

Even if you still need to manage the VMs, the list of tasks that you need to do is shorter.

  • You don’t need to backup the content
  • You don’t need to manage the hardware
  • You can scale the number of VMs automatically
  • You can serve content cross-location
  • Scaling is simple and faster

Additional to this, by keeping the content stored inside Azure Files you do not only have a backup solution that works out-of-the-box but you are also ready for what future might bring to us.

For example if in the future Azure Files would have support for access using Azure AD, than the only thing that you need to do is to move the access rights to Azure AD and stop the Azure VMs where File Server is running.

Conclusion
Unfortunately, except SharePoint solution, there are not too many options that would allow us out-of-the-box to have integration with AD roles.
An hybrid solution like the one with Azure VMs might be the most clean and straightforward solution until Azure Files would have new capabilities.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP