Why you should connect MS Teams and Dynamics 365 for Sales

MS Teams is just blowing up, isn’t it? In July of this year it hit 13 Million Active Daily Users and surpassed Slack!

I too, am experiencing a shift in my own usage of Teams. I now have the Teams desktop app open (and maximised) more than any other app on my laptop. That’s huge! Particularly when Outlook had previously held that position for the past 15 years!

So, we’re spending more time in Teams, and it is all the more important that we connect it to the other Apps we rely on so much. Dynamics 365 for Sales is one such app. Here are 3 reasons why the two are much better when they are connected.

1. Make your Opportunity Pipeline easily accessible.

If your sales team are spending increasing amounts of time collaborating in teams, then make it easy for them to access their Opportunity Pipelines and sales data without having to launch a browser window and navigate to Dynamics 365 for Sales.

Surface the Dynamics 365 for Sales Dashboard in Teams.

In Teams you can surface the dashboards from your Dynamics 365 for Sales App. You can also, configure a channel to display a list of records, whether this be leads, opportunities, accounts, contacts (or others)

2. Quickly search your Dynamics 365 for Sales Data

You can have a conversation (of sorts) with Dynamics 365, from right within Teams. Ask it to “Find Alan Roberts”, and it will return matching records or opportunities related to the contact. You then have the ability to preview the records.

What’s nice here is that, you can click on the email from the returned record, and it will launch Outlook. Click on the address and you are taken to Bing Maps. The one disappointing thing here is that seemingly, you cant click on the phone number and initiate a Teams call straight away. This seems like a bit of a missed opportunity (or it’s simply something I haven’t set up correctly!)

3. Collaborate on Opportunities, whether you are a Dynamics 365 user or not!

One of the main use cases for Dynamics 365 and Teams integration, is to create a team that relates to a single Dynamics 365 record. Lets say your organisation is working on a large opportunity, that multiple people within you team will need to contribute to. The Opportunity will be managed in Dynamics 365 for Sales, of course. This is where the opportunity value and probability will be tracked, along with all of the activities such as meetings and emails with the prospective client.

At some point however, a proposal document is going to be required, and there’s a good chance that multiple people from across the organisation are going to need to collaborate on this.

The first great thing about the integration at this point is that you can easily create a team for your Opportunity. And this can be used to track your internal conversations about the opportunity and to work collaboratively on your outputs.

The second great thing, is that users do not necessarily need to be Dynamics 365 for Sales users (e.g. have a D365 Sales subscription) in order to collaborate on the opportunity. If the Sales Team need to involve colleagues from the Product Development Department in order to complete the proposal, then they can do so, without the company incurring the cost of D365 subscriptions for the Product Development Department.

And so, we have a situation where Dynamics 365 users and Non Dynamics 365 users can work together, to collaborate on the proposal. This leads on to the 3rd great thing, in that regardless of who is accessing/editing the proposal, and regardless of whether they are accessing this from Teams or from within Dynamics 365, everyone is working on the SAME VERSION OF THE DOCUMENT.

Users can access/edit the document from within Teams

Or from within Dynamics 365

Same document, same version, no more emailing documents around and copy/pasting in content from multiple authors!

Summary

The Dynamics 365 and Teams integration is really going from strength to strength, and some of the capability referred to in this post is part of the enhanced integration being released this month as part of Microsoft’s release Wave 2.

Microsoft is ‘betting big’ on both these platforms, and in my opinion, when they are used together, they can deliver real business value.

3 Comments


  1. Is Teams integration only supported by 1st party D365 apps or can it be used with the PowerApps licenses?

    1. Author

      Hi Neils.
      This was a good question, and i didnt know the answer off the top of my head. So i think the situation is as follows. It appears that you can only connect teams to a Dynamics 365 Environment (So you cannot connect it to an environment that purely has a CDS database). However, within the Dynamics 365 Environment, you do not need to connect teams to one of the 1st Party Apps. If within your Dynamics 365 environment you have created your own model driven application, then you can connect teams to this. Therefore, in theory, you could have a set of users that are licenced under PowerApps, that are able to use the integration with a custom model driven app. That is correct to the best of my knowledge.
      As an aside, you can connect Teams to Canvas Apps, so perhaps it will not be long before you can connect to Model Driven Apps in a CDS environment. It seems like a logical next step!
      Carl

Leave a Reply

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