For Canadian callers, the outgoing name display does not currently work. When I make an outgoing phone call via MS Teams, the call recipient only sees my business number. They do not see my company name or any name associated with that number. In the US, there is a CNAME database that needs to be updated with a name for each phone number. In Canada, there is no database. The caller's phone company sends the caller's name, whether it is VoIP or traditional phone. Please, MS Teams, add a feature where Canadian customers can indicate what business name should appear on a call recipient's phone. Without this, customers might think I am a spam call if they don't have my phone number saved in their phone.

I have a large(ish) Team of 172 members and have at least a dozen instances of people telling me that they are getting notifications of new posts even though they have the channel notifications turned off or even have the channel itself hidden. I have verified that they have their notifications set to Off for "All new posts" and/or that they do indeed have the channel(s) hidden. They still get banner and Activity Feed notifications whenever there is a new post, even without any mentions at all.

I have provided a couple of screenshots to demonstrate. One is of the channel setting showing that the "All new posts" is Off. The other shows a notification in the Activity Feed for a post that was a reply in that channel to a post that I did not create.

We have probably around 100 Teams created and this only seems to happen in Teams that are large. I have gone so far as to create a brand new Team with a slightly different name and add the same members back in, essentially "re-creating" the Team with a brand new setup (hence the different name). That did not fix the issue either, although it affected different people after I created the new one. Some people have the issue in both Teams, some were fixed in the second one, some didn't start having the issue until the second one. This happens when using the Desktop App, the Web App, or the Mobile App so this definitely appears to be a bug on the backend rather than a client configuration.

I have performed the following steps in an attempt to troubleshoot:
1. Setting Notifications for the channel back to On, waiting about 10 minutes, changing them back to off.
2. Manually logging user out of Teams then logging back in.
3. Uninstalled/reinstalled the Teams desktop app.
4. Uninstalled Teams Desktop app, deleted the following folders manually, rebooted PC, then reinstalled Teams:

 a. "C:\Users\<user>\AppData\Local\Microsoft\Teams"

 b. "C:\Users\<user>\AppData\Local\Microsoft\TeamsMeetingAddin"

 c. "C:\Users\<user>\AppData\Local\Microsoft\TeamsPresenceAddin"

 d. "C:\Users\<user>\AppData\Roaming\Microsoft Teams"

 e. "C:\Users\<user>\AppData\Roaming\Microsoft\Teams"

Alas, nothing has worked.

Whenever you call someone in Microsoft Teams and they do not get your call, you can leave them a voice message in the app.

Teams will then send an email message to the recipient's mailbox with the voice message information, the transcription and an attached audio file. Teams will also send it from the caller's email address (e.g. From: John.Doe@example.com).

These email messages are sent in such a way that an Exchange Transport Rule like the one attached in the PNG file will flag them unexpectedly, because they seem to be sent from IP address(es) not included in the default SPF record for Office 365 customers:
v=spf1 include:spf.protection.outlook.com -all

If you analyze the headers of the affected email messages, you will probably find lines like the one below:

Authentication-Results: spf=fail (sender IP is 52.114.76.82)

Received-SPF: Fail (protection.outlook.com: domain of example.com does not
designate 52.114.76.82 as permitted sender) receiver=protection.outlook.com;
client-ip=52.114.76.82; helo=EUR03B.map.protection.outlook.com;

This is a well known issue of Teams as documented in their github repo:
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/Known-issues.md

Please, resolve this security problem at your earliest convenience.