CLOUDY MUSINGS

There's a very specific moment in almost every Azure File Sync conversation where things go from "this is going great" to "wait, what do you mean we can't do that?" P.S. That happened this week and it took me back, hence the blog post. This usually happens right after the POC looks successful. You've synced a few hundred gigs from the D: drive of an on-premises file server, cloud tiering is working, ACLs look intact, and everyone feels good. Then someone asks how you expose

So you're looking at Azure Data Box, and it seems pretty straightforward. Microsoft sends you a physical box, you load it up with data, ship it back, and boom: your data's in Azure. Simple, right? Then you actually start planning the migration. You open the portal, dive into the docs, and suddenly you're reading the same paragraph about "regions" for the third time, still not entirely sure what it means. Here's the question I've been asked from time to time: If I create my Da

a.k.a. How to migrate file data without breaking apps, users, or your weekends! All code for this blog can be found here ! In my time of supporting customers embracing a "digital transformation", every file migration starts the same way: “We just need to move our file shares to the cloud.” That sentence hides an enormous amount of complexity. Files are not just bytes on disk (I wish they were...life would be easier!). They encode how people collaborate, how applications behav