Martin Gibney - Microsoft Teams

With everything we can do in any O365 Admin Portal possible to do, even easier and better, in PowerShell, I have tried to create scripts to automate as much of my tasks as possible. When I run these manually its fine, I enter my credentials and approve my MFA popup on Authenticator App.  But what about scripts I want to run regularly, or automatically based on another event happening? Well, basically we need a few things. The first is to have an O365 Admin account, with only the bare minimum role we need, created and NOT enabled for MFA. This is a risk of course but if it can be restricted and controlled (think Conditional Access here) within your environment then this will be more of a benefit than it is a risk. Once we create this account, we now need to securely save the credentials somewhere so they can be used in an automated/scheduled task. Storing credentials securely Step 1: Store your credentials in a variable - for this session only On the server you are going to run your

Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &

Good news (sort of), yesterday, Jared Spataro, the Corporate Vice President for Microsoft 365 announced in a blog post  that the Audio Conferencing Addon CAL will be included as part of all Enterprise and Business CALS from 1st March 2022. This means that users can host Teams meetings and all of them will include the PSTN Dial in number for over 70 countries and 44 languages, without the need for the additional Audio Conference Addon CAL as we need now (or have A5/E5). This sounds great right? Free !!..... well not quite free, while it will be included with the CAL, the CALs themselves are actually going up in price at the same time, so the following (List price increases) applies: Office 365 E1 from $8 to $10 per user per month Office 365 E3 from $20 to $23 per user per month Office 365 E5 from $35 to $38 per user per month Microsoft 365 Business Basic from $5 to $6 per user per month Microsoft 365 Business Premium from $20 to $22 per user per month Microsoft 365 E3 from $32 to $36 pe