Microsoft Teams data into Azure and Power BI
Collaboration data from Teams
Yres has no standalone Teams connector: Teams data comes in through the Microsoft Graph API. You register one app in Microsoft Entra ID, assign it the Graph permissions for Teams and pick the Graph preset in Yres. Yres requests a token with OAuth2, reads the Graph endpoints for teams, channels and messages page by page, and writes the result to an Azure SQL database in your own tenant. From there you use the data in Power BI.
At a glance
- Connection
- Microsoft Graph API (version 1.0), through the Graph preset in Yres. There is no separate Teams connector
- Sign-in
- OAuth2 with an app registration in Microsoft Entra ID: client credentials, or authorization code with a refresh token
- Graph permissions
- Depending on your scenario, for example Team.ReadBasic.All, Channel.ReadBasic.All or ChannelMessage.Read.All, with admin consent
- Reach of the permissions
- Application permissions apply tenant-wide; the app does not have to be a member of a team
- Paging
- Yres follows the next-page link Graph returns with each page until everything has been fetched
- Where it runs
- Graph is publicly reachable over HTTPS, so the cloud runtime is sufficient. A self-hosted integration runtime is only needed when traffic must pass through a restricted network
- Secrets
- The app's details go to the Key Vault in your own Azure environment, not to the Yres web application
What you arrange yourself
- 1Register an app in the Microsoft Entra admin center (Identity → Applications → App registrations) and note the client ID and tenant ID.
- 2Create a client secret and copy the value immediately; it cannot be retrieved afterwards.
- 3Under API permissions, add the Microsoft Graph permissions for Teams that match your goal and have an administrator grant admin consent.
- 4Choose the grant type: Client Credentials for a background process without a user, or Authorization Code with a refresh token for access on behalf of a user.
- 5Add a source in Yres with the Graph preset and enter the tenant ID, client ID, secret and scope.
When you need this — and when you don't
A standalone connector is enough if…
If you only want to see how much Teams is being used, the usage reports in the Microsoft 365 admin center already show that. No data warehouse required.
Yres adds value if…
Yres earns its place when you want to combine Teams data with other sources, for instance teams and channels next to your HR or project administration, or when you want to record how the structure of teams and channels changes over time.
Frequently asked questions: Microsoft Teams
What is the difference between the Microsoft Teams source and the Microsoft Graph source in Yres?
Technically none: both use the same Graph preset, the same address and the same OAuth2 sign-in. The difference is in the permissions you give the Entra app. For Teams those are the Graph permissions for teams, channels and messages. The Graph page describes the same connection for Microsoft 365 in general.
Does the app have to join every team I want to read?
No. With application permissions the app gets tenant-wide access without being a member of any team. An administrator does have to grant admin consent. Pick only the permissions you really need: messages need a different permission (ChannelMessage.Read.All) than teams (Team.ReadBasic.All) or channels (Channel.ReadBasic.All).
When do I choose Authorization Code instead of Client Credentials?
Client Credentials is meant for a background process without a signed-in user and is the usual choice for scheduled loads. You use Authorization Code when access has to run on behalf of a user. In that case a refresh token is mandatory; Yres uses it to obtain a fresh access token on every run.
Which Teams data can I retrieve?
Whatever the Graph endpoints for Teams return and the granted permissions allow: teams, channels and messages. Microsoft's Teams API documentation lists the available endpoints; what the app may read from them is governed by the permissions.
Full technical description in the knowledge base →·Last reviewed:
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.