Teams administrations who have been using Set-CsUser (https://docs.microsoft.com/en-us/powershell/module/skype/set-csuser?view=skype-ps) to configure Microsoft Teams users’ voice settings will notice that it has stopped working as Microsoft has indicated early in 2022 that will be deprecated. The replacement
One of the past projects I worked on for a client was to help them move from a Mitel PBX phone system to Microsoft Teams as their phone system. Aside from the design and implementation
I’ve recently been involved in a manual migration of multiple subscriptions from a tenant to another due to an organization change and one of the components that I was responsible for was the migration of
I used to work with Microsoft Teams Direct Routing voice deployments quite often in the past before moving to a more Azure focused role so one of my ex-colleague recently reached out to me to
As a follow up to my previous post: Using PowerShell to send custom log data to Log Analytics for Azure Monitor alerting and Kusto Query https://blog.terenceluk.com/using-powershell-to-send-custom-log/ I recently looked into how the Certificates & secrets
As described in my previous post: Using PowerShell to send custom log data to Log Analytics for Azure Monitor alerting and Kusto Query https://blog.terenceluk.com/using-powershell-to-send-custom-log/ I had difficulty using Christopher Scott’s script to work when used
I’ve recently had to look into how the Certificates & secrets configured for their App Registrations could be monitored so administrators could be warned well ahead of the expiry so applications using these Enterprise Applications
As stated in the following Microsoft documentation: How Exchange Online uses TLS to secure email connections https://docs.microsoft.com/en-us/microsoft-365/compliance/exchange-online-uses-tls-to-secure-email-connections?view=o365-worldwide By default, Exchange Online always uses opportunistic TLS. Opportunistic TLS means Exchange Online always tries to encrypt connections
Problem You’ve completed configuring an Azure Function App with a PowerShell script that authenticates against Azure AD with Connect-AzureAD using a certificate but noticed that attempting to use the Test/Run button shows that the authentication
I’ve been working with a lot of automation in Azure lately and wanted to capture as many configuration activities I have gone through to share through my blog, and today’s post is to demonstrate how
