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.

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.

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.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.