Product Pageantry

Microsoft integrations — Dynamics, Outlook and Teams

I absolutely love Microsoft products. It’s just a warm fuzzy feeling I get when I know that I’m using a tool from a company that’s simply rock-solid reliable. Trouble? They’ll help me out. And they did. But this time, using Dynamics, i found quite a few reasons to doubt my all-encompassing love for MS.

It took me a lot of searching to find the right documentation for my issue. I finally raised a support ticket and asked them to send over the right documentation for my problem, because scheduling a call became a waiting game. Well, they sent over 2 documents, but when have 2 ever been enough in real life? I needed to go through a lot more fine print to find only a slightly clearer answer to my question. I’m still wondering why Skype has default calling protocol via Dynamics, when Teams isn’t? And why doesn’t Teams advertise its Business voice calling option loud and clear?

I’ve also tried tracking my email activities through Outlook. Why is the design such that I need to figure out so much to configure something that makes so much essential sense to a regular user?

How does this idea sound — putting a question mark link next to most features — which link around to Help Documentation on it. If we could find a way to design it well enough and such that all documentation is interlinked but clearly manageable, that would be great. Dynamics would become the easiest tool to learn and use. And being customer-centric is the priority.