Teams Mobile Feature updates for iOS

There are two handy features for the mobile client coming out quite soon. The first one is a better integration on the file storage integration. File-picker will soon (if not already for you) enable you to select different locations to attach files from. On my personal device, I can now pick from OneDrive, Google Drive and Dropbox. This feature should be rolling out to most tenants already The second feature coming out is the capability to hide (or show) Teams calls in the native iOS call log. I am looking forward to this as I have more than once accidentally called someone back with the wrong modality when I'm not in the office and not on Wi-Fi. Be aware that calls made prior to turning this feature off (removing calls from the call log). Already placed calls will remain in the list. The setting only applies to new calls. This last feature should be rolling out in September .

Autumn summary of news related to Exchange

Starting this post with two Exchange Online updates. 

Let me begin with a quick user tip: Finding the perfect time for a meeting with participants outside of the company can sometimes be a challenge. I have been using "Find Time" for a long time. But now that add-in is now being replaced by a native scheduling poll feature. Collaboration just got easier!

As many of you probably already know, Microsoft is starting their selective shut down of Basic Authentication on October the 1st (today) 2022. Working with customers I find that many of them have enabled MFA for their users, and these users will not be affected by the change. However, there are a lot of 3.rd party integrations out there, using EWS and other affected services. And these integrations will stop working once basic authentication is shut down.

I wanted to share two easy ways for an organization to figure out if they have such services running or not. 

The easy one requires licenses for conditional access, and use of  log analytics. Simply create a conditional access rule blocking all legacy authentication, and set it to report only. Within a day or two, you can go to the analytics part of conditional access and see how may "fails" there are. The report will identify any user-id being hit by the report only block.

The other method can be performed by filtering the sign-in logs in Azure AD. Head over to the Entra portal (, open "monitoring and health" and select "sign-in logs". Add a filter called "client app", and use the filter to select on  all or any of the legacy protocols, "pro tip: I also add a filter for successful logins, failure attempts can also be password spraying"