In order to use this component, you just need to fill in the proper configurations to make sure Microsoft Teams can be correctly authenticated to your account.

To do so, you need to set the site properties values:

Regarding setting up your Azure account for it, if you have a Microsoft Azure administrator, s/he would know how to set it up those for you. Otherwise, you need to get them on your Azure Portal.

• ClientId: The Application (client) ID that the Azure portal – App registrations experience assigned to your app.
• ClientSecret: The application secret that you created in the app registration portal for your app. You shouldn't use the application secret in a native app or single page app because client_secrets can't be reliably stored on devices or web pages. It's required for web apps and web APIs, which have the ability to store the client_secret securely on the server side. The client secret must be URL-encoded before being sent.
• Password
• Scope: A space-separated list of scopes that you want the user to consent to. For the /authorize leg of the request, this can cover multiple resources, allowing your app to get consent for multiple web APIs you want to call.
• TenantGUID: The {tenant} value in the path of the request can be used to control who can sign into the application. The allowed values are common, organizations, consumers, and tenant identifiers.
• Username

Take a look on this video on how to create an Application in Azure and get their API credentials or follow official Microsoft documentation here. Take into account the user you will be using on the OutSystems - Teams integration (the one you will get the Username and Password properties from) needs to be granted the set of permissions to do the Microsoft Teams operations you will be doing (for example, see here the permissions needed to successfully call the list channel API).

Last but not least, you can refer to the article Microsoft Teams integration with OutSystems and Microsoft Graph API documentation.