man showing distress

Cloud Frustration

Am I alone? Probably not.

One of the pros and cons that come with cloud-based technologies is the speed with which things change. On the pro side, it usually means we’re getting more features, more capabilities, and more potential for business value and/or productivity gains – usually at a faster pace than were released pre-cloud. On the con side, we have the challenges of keeping up: Keeping up with how to use new features, updates with how to use existing features, how to navigate changing interfaces, and the always fun deprecation of features. Finally, there are ongoing challenges to find accurate help as it’s challenging for both platform owners and training materials creators to keep up with production rollouts.

As users at all levels, we’re faced with questions – and often the same ones over and over…

  • Is something wrong with my tenant/instance?
  • Is there something wrong with my environment or configuration that doesn’t match current documentation?
  • Is something wrong with the documentation? Is documentation current?
  • Am I doing something wrong? (One could argue this should be listed first…)

At the moment, I’m working on presentation updates, screen shots, etc. and running into all sorts of weirdness, which is frustrating. I want to get behind Dataverse. I really do. Running into this stuff every time I step away and then come back, I seem to hit this. I can’t be the only one. I fear this same issue is too common for folks new to the platform which are usually my target audience. Hopefully Microsoft can clean it up a bit.



    1. I *think* it’s mostly “cloud timing” issues. Create something, wait undetermined or uncommunicated amount of time before it shows up with more wonky time before it’s fully functional… Similar to what we see in Teams, SPO, etc. But there are also plenty of labeling inconsistencies as well… I am pretty biased though. 😉

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.