Please add a new lab showing how to notify users using the Teams Activity Feed via the Graph API

Fabian Williams suggested a new lab specifically about the Graph API

This is a great idea IMO and here are some ideas:

• Proper use of Graph SDK
• Elevating privilege with app permissions
• Handling throttling
• Browsing large datasets by paging
• Using webhooks / change notifications for bulk data synchronization

Now A01-A03, B01-B04, and "ConfigurableTab" labs.
These are from Waldek and some but not all have been addressed in the update. Need to review and check.
(Thanks @waldekmastykarz)

More issues from @waldekmastykarz

pointed out that azure-ad-jwt hasn't been updated in 4 years; want to find the best approach (Passport?)

For a GET request you don't need to set the content-type header:

TeamsAppCamp1/A01-Start-AAD/server/identityService.js

Line 130 in 8c00ca5

"Content-Type": "application/json",
Also, to be compliant with HTTP/2, all request headers' names should be lowercase (not necessary for Graph at this time but best practice)

In lab A03, you mention to update devDependencies in package.json to add adm-zip, but if you have a lockfile (which is a default these days) if you run npm i, the changes won't be picked up because npm will only install packages from the lockfile, so it would be better to say: run npm i -D adm-zip

Here: https://github.com/OfficeDev/TeamsAppCamp1/blob/main/Labs/Labs-A/Lab-A03.md#step-1-add-a-module-with-teams-helper-functions, the inTeams function is async but there's no need for async really, unless you're going to modify it later on and want to keep the number of steps lower

RE: manifest versions: JS advocates pointed out that it would make sense to maintain the version in package.json and then sync it to the manifest. It's a small detail, but something that would feel natural to JS devs and also allow them to maintain the app version in just one place

Lab 5, Step 2: in the code sample you could skip the if (employee) { check because just above you verified the opposite and redirect to a different page if it's the case, so this extra check is unnecessary:

I just noticed that you didn't commit lock files to the repo. To ensure that this code will run in the future, it would be good to include them. Otherwise, if one of the dependency changes, it could break the whole sample

The app in App Camp is already multi-tenant but the labs don't explain how to run it in other tenants. This lab would guide the student through running the Northwind Orders app in any tenant by creating a service principal and getting administrator consent.

Add a new lab showing how to notify users using a proactive bot

Please add a new lab showing how to build a conversational bot that works multi-tenant
Probably using Bot Framework SDK and LUIS

The current switch case will not support browser as the app is not inside any M365 host app and hence no context.
Handle default styling outside inM365() condition.

Please add a new lab showing how to build a meeting app

Per Halaa's input today

All exercises should use consistent formatting for file names, function names, etc.
Luise Freese kindly provided this guide: https://docs.microsoft.com/en-us/style-guide/developer-content/formatting-developer-text-elements.

Pretty sure we are still random on this and need to do an overhaul on all labs.

I followed the steps in A01 but end up with an infinite login loop here. I'm using the admin@ account. It has an employee ID and a manager. Any idea where I went wrong? I started ngrok with out --host-header because I don't have a paid subscription.

While working on the lab I found that "on my PC" :) HOSTNAME is replaced by my real system HOSTNAME.

HOSTNAME variable defined in .env did not overwrite the real HOSTNAME system variable.

The problem disappeared after I changed HOSTNAME=something.ngrok.io to HOSTNAME123=something.ngrok.io and all process.env.HOSTNAME to process.env.HOSTNAME123

Following the release of v4 and the general availability of Teams Toolkit at Microsoft Build, it would be great if the samples in the App Camp could be made compatible to be opened in Teams Toolkit, this would enable developers to use the feature sets in the toolkit to be more productive and provide a more consistent approach to app development.

Using the Toolkit could help new developers get up to speed more quickly and reduce the effort required on setup tasks i.e. auth, manifest creation etc.

Please test and fix for free version of ngrok