Product

What MS Teams scope does Profit.co use for Messaging? Describe the messaging process.

Introduction

Microsoft Teams is a collaboration app that helps your team stay organized and have conversations in one place. To enjoy the advantage of added workplace productivity, Profit.co has integrated with Microsoft Teams that enables you to easily manage, monitor, review and check in your OKRs from and within Microsoft Teams. With this duo integration, you can access information from anywhere and at any time with secured cloud storage and can kickstart access right from Profit.co instead of switching platforms. Integrating OKRs with Microsoft can help you access information from anywhere and at any time with secured cloud storage and can kickstart access right from Profit.co instead of switching platforms.

Let’s see how to install Profit.co using the MS graph API with the scope:

Installation & Authentication Process

Step 1:

Install Profit.co bot from the app store.

Please refer how to install Profit.co bot on MS Teams

Step 2:

Once the bot is installed, the bot has to be authenticated with your Profit.co account. This process links your Profit.co bot with your Profit.co account. To perform this step, just enter “login” in the bot.

Step 3:

This opens a panel to login:

Step 4:

Here, we have two ways to authenticate with your profit.co account.

  • Use your Profit.co’s username and password.
  • Simply click “office 365” to authenticate your profit.co through OAuth2 (SSO).
  • You can use your office 365 credentials to login.

Step 5:

Here, Profit.co will ask for your permission to sign you in and use your profile information. The exact MS Teams scope name that is requested here is:

email opened profile User.Read

Step 6:

Using this scope, Profit.co gets:

  • Email address of the logged in user
  • Tenant id
  • Access & refresh tokens

These will be used to push the message from your Profit.co cloud application to the bot.

Messaging between Profit.co & MS Teams

  • Whenever a message needs to be delivered to a user, the Access token will be used to post the message to the bot with the MS graph API. This access token expires periodically — default is 90days, but can be changed by the admin.
  • When the access token expires, we’ll use the Refresh token to regenerate a new access token.
  • Tenant id is used to identify the account where the data has to be posted.
  • These tokens and tenant Id will persist in Profit.co, and used in the messaging calls using the Microsoft graph APIs to push data to the bot. Please, refer to the doc for further details about the tokens.

Please, refer the doc for further details about the tokens.

Profit.co helps you to integrate with your favorite apps, You can integrate with Jira, Slack, G Suite, Zapier, Teams, Office 365, and 30+ apps. You can connect with Profit.co OKR Software to integrate users, and tasks, and also check in your key results within the apps. Check out our wide range of integrations and get connected instantly.

kradhakrishnan

Share
Published by
kradhakrishnan

Recent Posts

Career Development Plans That Drive Engagement

Work has changed.People no longer see their jobs as simply a paycheck or a place…

1 week ago

How the Say-Do Ratio Helps Measure Commitment in Agile Teams

Agile teams live on a steady diet of promises and proof. At sprint planning the…

1 week ago

Why is Culture Important to the Success of a Merger & Acquisition Strategy?

Many companies begin discussing mergers and acquisitions with meticulous plans and comprehensive financial models. But…

1 week ago

Why focusing on HRIS performance alone hurts the business

For years, people thought that performance management was an HR job, with forms, ratings, and…

1 week ago

Why Your Billion-Dollar Merger Is Probably Killing Innovation

Consider this scenario: when a Fortune 100 company bought a cloud startup for $2.3 billion,…

1 week ago

What is the Link Between Employee Wellbeing and Engagement?

What is Employee Wellbeing? Employee wellbeing is one of those topics that sounds simple until…

1 week ago