These features are currently available:
When starting the extension for the first time it will ask you for two IDs: The Application ID and the Directory ID. Your organization's Microsoft admin should be able to provide you these IDs after following the admin setup guide provided below. After you've entered them you'll be able to login with your Microsoft account.
Before your users can use this extension, you as a Microsoft admin of your organization has to prepare the connection in the Azure Portal by creating an app registration. This only has to be performed once for all users of your organization.
These are the steps:
Open the Azure Portal
Navigate to Azure Active Directory
Navigate to App registrations
Click + New registration in the toolbar
https://raycast.com/redirect?packageName=Extension
In the newly created app registration, navigate to API permissions:
Click + Add a permission, select Microsoft Graph → Delegated permissions, search for "presence", check Presence.ReadWrite
and click Add permissions.
Repeat the same steps to get this list of permissions:
Channel.ReadBasic.All
Chat.Read
offline_access
Presence.ReadWrite
User.Read.All
Presence.Read.All
- needed for getting the presence of other usersClick the button Grant admin consent for undefined to give these permissions to your users in the name of your organization.
There's nothing to fear here: Even with these permissions, your users will only be able to access things they are allowed to see.
That's it! Now navigate to the Overview of your app registration and note down the Application (client) ID and the Directory (tenant) ID. Your users require these two IDs to connect their Raycast with Microsoft Teams.
Relax: These two IDs are no secrets and don't provide any access at all when used alone. Each user still additionally needs to authenticate using his/her Microsoft Account. You can easily provide these IDs in your internal documentation.