Build a Microsoft Teams Bot: Kudos App Development -- 2
Budget: $250 – $750 USD
We are looking for an experienced Microsoft Teams app developer to integrate our Kudos app (Angular + Firebase backend) into Microsoft Teams. The goal is to allow users to create, share, and engage with kudos boards directly within Teams, while ensuring seamless integration with our existing platform.
== Scope of Work ==
Teams Tab App –
Enable users to view, create, and manage kudos boards within a Teams tab.
Kudos Bot for Teams –
Assist users with board-related actions (e.g., subscribe to boards, get new message notifications, create a board etc.).
Board Sharing & Invitations –
Integrate with Teams to share boards and invite colleagues directly.
Notifications & Delivery Updates – Send kudos delivery alerts and board updates as Teams notifications.
Authentication & Permissions – Ensure secure login via Firebase Authentication or Microsoft Entra.
== Required Skills ==
1/ Microsoft Teams App Development (Bots, Tabs, Adaptive Cards)
2/ Microsoft Bot Framework & Graph API
3/ Firebase (Firestore, Cloud Functions, Authentication)
4/ Angular (for UI modifications if needed)
5/ Authentication
6/ CI/CD Deployment for Teams Apps is a plus.
7/ AWS Lambda
== Please note - KEY REQUIREMENT ==
We need to use AWS Lambda and other AWS services or Firebase for all backend, not Microsoft cloud. This is a key requirement. We can use Microsoft Authentication for Teams though, but rest should be on AWS and Firebase only.
== How to Apply ==
Please send -
1/ Your experience with Microsoft Teams integration & Firebase.
2/ Estimated timeline, budget and approach for the project.
3/ Any relevant projects or demos showcasing similar work.
Looking forward to working with you! ?
== FAQs ==
1/ Are there any specific design guidelines or branding requirements for the Teams tab UI?
To be provided 1/ design guidance and 2/ reference app
The design and branding should reflect the brand, but the focus is more on functionality.
2/ Should the kudos boards sync in real time (e.g., via WebSockets), or is periodic refresh sufficient?
The boards already exist. The teams app will allow users to receive notifications on their teams (for any messages added on the board), receive board delivery notifications, share a board within a group, and add messages to a board just by replying to it.
Just simply think of it this ways - there will be two apis:
API 1: Teams app can query this api for board information, and sending data (e.g. add message etc.
API 2: Teams app will provide this api, and the board can call this api to send data to the teams app (notifications etc.)
3/ What exact actions should the bot perform? Examples: subscribing to boards, creating boards, managing notifications?
Subscribe to board messages
Board delivery notifications
Share a board in a teams group
Create a board (just a link in the tab that loads this url: TO BE PROVIDED)
Invite users to a board - when users are invited, they receive a notification in their teams chat.
4/ Should the bot respond to direct user queries or only send proactive notifications?
Just a few basic commands supported like ‘create-board’ will call an api to create board, and provide the link. You can use a dummy API from the internet for this for now.
4/ Are there any pre-defined message templates or formats for notifications?
None yet. We’ll revise it later. Focus is more on functionality, less on design here.
5/ Should board invitations integrate with Teams channels and group chats, or just individual users?
All three.
6/ Is there a need for email-based invitations outside of Teams, or is it restricted to Teams users only?
Only teams users.
7/ Should notifications use Teams Activity Feed, bot messages, or both?
Ideally both and the user can choose. We can start with one.
8/ Are there any specific triggers or workflows for delivering notifications (e.g., when a new kudos is added, when a user reacts to a kudos)?
Yes, will be able to trigger an api when a new kudos is added or when a user reacts.
9/ Can you confirm that all backend operations should be performed exclusively using AWS Lambda and Firebase? (No reliance on Microsoft Azure backend services.)
That’s right! You might still need Microsoft Entra for authentication though, but let’s not use Azure at all and avoid where possible.
10/ Do you have any existing pipelines or preferences for deploying Teams apps?
We can skip pipeline integration for now.
11/ Should the developer set up the app in your Teams environment, or will it be handled internally?
Can you create a new account, set up the app in the store, and pass the credentials?
12/ Will all Teams users have the same level of access to the Kudos app, or are there specific roles (e.g., admin vs. regular user)?
Same access. The access is already guarded at the main website.
13/ Should access to certain boards or features be restricted based on Teams roles or Firebase roles?
No.
14/ Do you have a staging environment in Teams for testing the integration?
Not required. But feel free to create a staging app for testing.
15/ What is your expected timeline for completion?
Sooner the better, but negotiable.
16/ Are there any milestones or specific deliverables (e.g., working tab app first, then bot integration)?
Board Notifications is the first priority.
Tab is after that.
== Scope of Work ==
Teams Tab App –
Enable users to view, create, and manage kudos boards within a Teams tab.
Kudos Bot for Teams –
Assist users with board-related actions (e.g., subscribe to boards, get new message notifications, create a board etc.).
Board Sharing & Invitations –
Integrate with Teams to share boards and invite colleagues directly.
Notifications & Delivery Updates – Send kudos delivery alerts and board updates as Teams notifications.
Authentication & Permissions – Ensure secure login via Firebase Authentication or Microsoft Entra.
== Required Skills ==
1/ Microsoft Teams App Development (Bots, Tabs, Adaptive Cards)
2/ Microsoft Bot Framework & Graph API
3/ Firebase (Firestore, Cloud Functions, Authentication)
4/ Angular (for UI modifications if needed)
5/ Authentication
6/ CI/CD Deployment for Teams Apps is a plus.
7/ AWS Lambda
== Please note - KEY REQUIREMENT ==
We need to use AWS Lambda and other AWS services or Firebase for all backend, not Microsoft cloud. This is a key requirement. We can use Microsoft Authentication for Teams though, but rest should be on AWS and Firebase only.
== How to Apply ==
Please send -
1/ Your experience with Microsoft Teams integration & Firebase.
2/ Estimated timeline, budget and approach for the project.
3/ Any relevant projects or demos showcasing similar work.
Looking forward to working with you! ?
== FAQs ==
1/ Are there any specific design guidelines or branding requirements for the Teams tab UI?
To be provided 1/ design guidance and 2/ reference app
The design and branding should reflect the brand, but the focus is more on functionality.
2/ Should the kudos boards sync in real time (e.g., via WebSockets), or is periodic refresh sufficient?
The boards already exist. The teams app will allow users to receive notifications on their teams (for any messages added on the board), receive board delivery notifications, share a board within a group, and add messages to a board just by replying to it.
Just simply think of it this ways - there will be two apis:
API 1: Teams app can query this api for board information, and sending data (e.g. add message etc.
API 2: Teams app will provide this api, and the board can call this api to send data to the teams app (notifications etc.)
3/ What exact actions should the bot perform? Examples: subscribing to boards, creating boards, managing notifications?
Subscribe to board messages
Board delivery notifications
Share a board in a teams group
Create a board (just a link in the tab that loads this url: TO BE PROVIDED)
Invite users to a board - when users are invited, they receive a notification in their teams chat.
4/ Should the bot respond to direct user queries or only send proactive notifications?
Just a few basic commands supported like ‘create-board’ will call an api to create board, and provide the link. You can use a dummy API from the internet for this for now.
4/ Are there any pre-defined message templates or formats for notifications?
None yet. We’ll revise it later. Focus is more on functionality, less on design here.
5/ Should board invitations integrate with Teams channels and group chats, or just individual users?
All three.
6/ Is there a need for email-based invitations outside of Teams, or is it restricted to Teams users only?
Only teams users.
7/ Should notifications use Teams Activity Feed, bot messages, or both?
Ideally both and the user can choose. We can start with one.
8/ Are there any specific triggers or workflows for delivering notifications (e.g., when a new kudos is added, when a user reacts to a kudos)?
Yes, will be able to trigger an api when a new kudos is added or when a user reacts.
9/ Can you confirm that all backend operations should be performed exclusively using AWS Lambda and Firebase? (No reliance on Microsoft Azure backend services.)
That’s right! You might still need Microsoft Entra for authentication though, but let’s not use Azure at all and avoid where possible.
10/ Do you have any existing pipelines or preferences for deploying Teams apps?
We can skip pipeline integration for now.
11/ Should the developer set up the app in your Teams environment, or will it be handled internally?
Can you create a new account, set up the app in the store, and pass the credentials?
12/ Will all Teams users have the same level of access to the Kudos app, or are there specific roles (e.g., admin vs. regular user)?
Same access. The access is already guarded at the main website.
13/ Should access to certain boards or features be restricted based on Teams roles or Firebase roles?
No.
14/ Do you have a staging environment in Teams for testing the integration?
Not required. But feel free to create a staging app for testing.
15/ What is your expected timeline for completion?
Sooner the better, but negotiable.
16/ Are there any milestones or specific deliverables (e.g., working tab app first, then bot integration)?
Board Notifications is the first priority.
Tab is after that.