Introduction When using Office applications, such as Outlook, you will see the presence and contact cards that appear when hovering over a user. From here you can initiate actions such as an IM or call etc. This is all based on the “DefaultIMApp” value in the current user's registry. If the user is using Skype for Business, this does not need any action from the user. However, in Teams, this needs to be enabled by the user under settings in Teams:
Whilst Flow does have some integration with Microsoft Teams, one missing feature is the ability to create a Team in Microsoft Teams (you can create Channels, messages etc.). With recent additions to Graph API, you can create a Team using a template and a Graph API call. This API call can be used within a flow. In this scenario, I'm going to create a flow to create a Team. This will work like so:
Microsoft Teams has a feature that I don't see used or talked about a whole lot - Cards. Cards allow you to post a container to a Teams channel. The type of card I will use here is a Message Card. These can contain text, images, links etc. Message Cards are not to be confused with Adaptive Cards. These are entirely different and are not exclusive to Teams. Adaptive cards are more flexible and interactive than Message Cards but unfortunately, do not support the method I employ here - Incoming Webhook.
Introduction Following on from Part 1, you should now have an AudioCodes SBC up and running in Azure. This article will cover any Azure specific setup to allow Teams Direct Routing to function. For Direct Routing configuration you can follow my earlier blog post for instructions. Note: In Azure, we are using a single NIC, so the “LAN” and “WAN” NIC mentioned is the same interface, so bear this in mind when configuring Media Realms, SIP interfaces etc.
This article is now out-of-date, please refer to this article for Deploying an AudioCodes SBC in Azure using the Azure Marketplace. Introduction I've written in the past about deploying AudioCodes SBC into Azure by using Azure Site Recovery. Whilst this works, it's not supported! I recently asked AudioCodes if there were any plans to officially release an “Azure Edition” of the SBC and to my surprise, they said “Yes”. It's about to hit GA, but I've been given a pre-release build to try.
Background With the preview release of Teams Direct Routing users are now able to make and receive PSTN calls using certified SBCs instead of Calling Plans. Part of setting this up involves setting up PSTN Usages, Voice Routes, Online Voice Routing Policies, PSTN Gateways etc. within Skype Online PowerShell. Much like Skype for Business, if your users have multiple calling requirements the amount of Voice Routes, PSTN Usages etc. can grow quickly and sometimes make it quite hard to fathom how a call will route.
Just a quick one here. I was busy setting up some Voice Routes and Online Voice Routing Policies for Direct Routing but it wasn't behaving as I expected. I had purposely locked down my account I was using to only allow UK calls. But when making a call to Microsoft US, it worked. Odd! I double checked the routing I had in place and it was correct. Strange… I then made sure I didn't have a Calling Plan assigned (as that will be used as a last resort)… I didn't.
Introduction Last Updated: 13/05/19 Microsoft has released Direct Routing for Microsoft Teams. This is one of the big steps – in my opinion – of making parity with Skype Online. Direct Routing effectively allows you to connect up existing PSTN connectivity (e.g. SIP trunks) into a certified SBC and route directly to Teams. This differs from the Skype Online method of doing this, in that you no longer need any hardware (on-premises Skype for Business Server or a CCE) other than an SBC.
Recently added to Skype Online and Teams is the ability to block inbound calls based on their caller ID. Useful for blocking nuisance callers. Once you've added the patterns, you ideally want to know: If the calling numbers you want to block will be caught in your patterns. Regex is not my strong suit so want to make sure it will match. Are some calls going to be inadvertently blocked?
Backup-TeamsChat Disclaimer: This tool is provided ‘as-is’ without any warranty or support. Use of this tool is at your own risk and I accept no responsibility for any damage caused. Backup Teams chat messages (not channel messages) for safe keeping - messages are saved in to a HTML report for easy viewing. Written in PowerShell Core and using Graph API (no modules required), it can be used on Windows, Mac and Linux.