Funky Teams Audio Conferencing behavior

Added some new users recently who do not have phones. I’m accustomed to adding an AD Attribute to the Proxy Addresses section for the SIP:user@domain.com attribute when they have a phone. Because these users don’t, I didn’t.

Apparently, the configuration we have requires this for the Teams Audio Conferencing details to even populate on the user. Without it they can still create and participate in meetings, they just never get the phone number from the audio conferencing assigned.

Once the attribute syncs to Azure AD the audio conferencing info populates right away.

How to create a file drop in Teams

Actually, this is to create a file folder in Teams that will move files to another (private) location whenever a new file is dropped in there. Why would you want to do that? You might want to get files in a semi-secure manner but then not have them live in a viewable location. Think, budgets from the CFO that others shouldn’t see.

Using Flow, create a new flow with the Sharepoint “When a file is created (properties only)” trigger. The Folder field needs to be populated with the file folder you’re watching.

Add an action for Sharepoint “Move file”. The File to Move field needs to be a dynamic action of “Identifier”. The Destination Site Address and Destination Folder may not be discoverable, so you’ll need to populate those with the correct target location.

One final note, I’m pretty sure the person adding the flow needs to be an Owner of the team, although I haven’t tested that.