I'm curious to hear from other system admins on how you manage environments with multiple cloud storage platforms in use. In my experience, it often gets fragmented over time—one department swears by Google Drive, while another opts for OneDrive due to Microsoft licensing. I've noticed that Dropbox is still lingering from previous setups too. This situation seems to lead to issues, especially with visibility. When users reach out for help in locating documents, it's not always clear which platform they're on, and searching across multiple services can be time-consuming.
The complications really add up when teams want to transfer files between different platforms or when there's a push to standardize on one service. These projects can quickly become chaotic, depending on the amount of data involved. I'm interested in how others navigate this challenge.
Do you aim to consolidate everything into a single platform, or do you accept that multiple services will coexist and adjust your processes accordingly? Additionally, are there any workflows or tools that you find helpful in managing files across various cloud platforms from an administrative standpoint?
5 Answers
Before picking a migration strategy, I suggest looking into Defender for Cloud Apps if you’re using M365 E5 or their standalone add-on. It helps discover shadow IT in your environment, giving you a concrete list of what cloud apps are in use. This fragmentation can also lead to compliance issues, especially in regulated industries. Having this kind of visibility can help you make informed decisions about consolidation.
In practice, many environments end up being a mix for a while, especially after mergers or when different departments start using their own tools. I recommend defining one primary platform going forward (like M365/OneDrive) and gradually moving teams there. Those legacy platforms tend to stick around until the data naturally phases out or a project necessitates a shift. Documentation and governance can really help clear things up, like having set rules for internal collaboration or data storage. Some teams implement indexing/search tools that work across platforms, but fragmentation will always exist when multiple services are allowed.
That approach aligns with what I see too. Steering new initiatives toward one platform avoids big disruptions. It's funny how mergers really kick off fragmentation, huh? When creating those rules, do you find that admins use indexing/search tools from DLP suites or independent tools?
We set a policy to only use approved platforms, which means blocking everything else. In our case, that’s only OneDrive and SharePoint. If you're thinking about backup services across all of these, that's quite a expense—it's better to consolidate to just one!
That makes sense! Having a few approved platforms seems like the cleanest option. Do you get pushback from teams when their preferred tools are blocked? I've seen departments try to sneak in their own choices if they don't feel the approved ones meet their needs.
You'd be surprised! It shouldn't be IT's job to hunt for documents. If users can't find something, that’s on management. But for Google Drive, there are tools like rclone which can help with cross-platform file management.
Totally agree! Ideally, IT shouldn't be the go-to for file hunting. But I get it—sometimes, users have no clue where files ended up after being shared. I’ve heard rclone works wonders for migrations and daily tasks too. Do you use it for both?
I’ve noticed that consolidation often leads back to Microsoft/Azure. It has just enough features to satisfy most departments, and honestly, the employees have given up on complaining. It complicates the management side when everything’s split up though. I usually try to migrate teams gradually when it’s less disruptive. You can say, "Let's start saving in this new spot."
When there’s a problem, tackle it head-on, otherwise people just get used to the old tools.
That sounds realistic. Many places drift toward the Microsoft stack simply because it meets most needs. I like your gradual approach to migration—big moves can turn into nightmares! When you shift teams over, do you migrate their old data too or leave that behind?
Great point! Gaining visibility first can definitely ground the discussion. Without it, you're left guessing about what's actually in use versus what IT thinks is there. Have you uncovered a lot of unexpected services by using Defender for Cloud Apps?