Microsoft Teams 1:1 PSTN (Public Switched Telephone Network) recording does what it says on the tin!
At the time of testing the recordings are placed in the user’s OneDrive “Recordings” folder as a MP4 file. As I mention in the video below this allows the recording to be easily shared, marked for retention or even be linked to a Power Automate flow.
This feature is is intended to support user initiated On Demand use cases, for Compliance recording Teams provides robust Policy Based Recording functionality.
Check out this 90 second video that shows 1:1 PSTN recording in action:
Note: 1:1 PSTN Recording is not on by default and has to be enabled via the Microsoft Teams PowerShell module. The command I used to enable recording for my demo tenant’s Global calling policy was:
Set-CsTeamsCallingPolicy -Identity Global -AllowCloudRecordingForCalls $True
Viva Topics leverages AI services from the Microsoft Cloud to pull together and surface knowledge for users to quickly and easily consume. More details on how Topics are discovered and curated can be found in the Microsoft Documentation. When a user navigates through Modern SharePoint pages or types a relevant query into Microsoft Search they are presented with a Topic Card that provides a summary for the specific subject the Topic covers. The end users simply view the details to dive deeper.
So what about security? The key point to know is that Viva Topics complies with an organisation’s Microsoft 365 security settings so that end users will only ever see content they already have permission to access. More details can be found in the Security and Privacy chapter of the docs.
Clear as mud? To help, I’ve created this 4 minute video to provide a concise overview of some of the main components of Topics and highlight where the cards are currently presented. Over time Topic Cards will start to appear across Microsoft 365 services such as Teams. There are also plans to link Topics to 3rd party content using Graph Connectors and future APIs will allow for new custom use cases.
If you want to access some free training on Viva Topics check out the modules on Microsoft Learn.
Viva Connections provides a company branded home page experience that can be surfaced directly within Microsoft Teams as a personal App. Some of the aims of Viva Connections are to keep an organisation connected, provide an easy way to allow people to contribute and allow the company to come together. In its current iteration Viva Connections is available for Microsoft Teams Desktops, although the mobile experience has been announced and should be available in the near future.
If you review the Viva Connections Resource Centre you can get a glimpse of the mobile version of Connections as well as the custom dashboard experience that’s planned.
I created the following 4 minute video to demonstrate the “nuts and bolts” of Viva Connection as it exists today (May 2021). I’ll reference this blog as a starting point in future posts as Connections evolves.
Historically, to deploy a phone you could type credentials directly into the device or use the phone sign-in web page. Recently, a third method was introduced that allows an administrator to work with a technician to provision the phone in the admin portal and then to remotely sign-in the device. Check out the documentation for more information, including details of the phone firmware required.
The following 2 minute video provides a simple demo of the remote provisioning and sign in experience.
Note: The most likely use case for this type of provisioning is the deployment of shared Android devices such as Common Area Phones.
I’ve jut started to look at Viva so I can help Microsoft Partners build practices and solutions. As you are probably area Syntex is one of the underlying components. I put together this demonstration to run through the Form Processing model creation process. I also triggered a Power Automate flow to perform additional processing using some of the outputs from my model.
To keep things real I used my own quote form I built using a standard Microsoft Word template. It has a straight forward format but as I was building my first model I decided not to over complicate things. I also triggered a Power Automate flow after the AI analysis had completed to prove I could do something useful with the results.
The ability to surface a Call Queue as a tab within a Channel adds new value to one of the main cornerstones of the Microsoft Teams Hub. For example, a Support Team can add their voice queue directly into a Channel within their Microsoft Team to provide a more collaborative agent experience.
I created this short video to provide an overview of this functionality. As you’ll see it’s really easy to configure from an admin perspective and the resulting “Call” tab automatically appears in the assigned Teams Channel.
Note: At the time of posting this functionality is very new, so be sure to refer to the Microsoft documentation to check for any changes in the agent experience and for new features that may be been added over time.
The Microsoft Call Queue feature article can be found here.
Note: The video above provides an an overview of what’s available with Standard Teams Room licensing. There is also a Premium SKU that signs a MTR up to Microsoft’s own comprehensive monitoring service. The details of which can be found here.
Warning: Your organisation may have locked down this capability but if you work on Microsoft Teams it is still worth knowing that it’s technically possible. If you are an admin and you have not put controls in place, then you may decide to take action.
One of my colleagues recently asked if there was an easy way to move hundreds of users between Teams? He owned both Teams but was not a Microsoft Tenant Admin.
To be totally honest it took me a while to “remember” but it dawned on me that good old PowerShell might be the answer. One of the nice things about the Teams Module is that is does allow Owners to perform actions on their Microsoft Teams. For anyone who is a Microsoft IT Pro what comes next is probably trivial but there are loads of technically minded people out there who are not familiar with PowerShell and who are Microsoft Team owners. This post is aimed at these folks.
I’ve created the short video below that provides the answer to the “moving users” question.
If you are new to the Teams PowerShell module you can get started by reading the documentation.
In case it helps the commands I used in the video are provided below:
Note: You will need to replace the Team’s GroupIds (ObjectIDs) with your own. If your tenant admin has not switched off access you can to do this by logging onto your Azure Portal (https://portal.azure.com) using your Microsoft 365 credentials and navigating to Groups, which live under Azure AD. The Export-CSV command will create the AppTest.csv file for you.
Hopefully, this has provided some food for thought?
As you may already be aware the shift from “classic” Stream to “new” Stream, which uses OneDrive for Private Teams Meetings (Channel Meetings use SharePoint) has been in the pipeline since last year. If you are unfamiliar with this change, go to this document to learn more about the architectural impact and roll out schedule. Even if you opted out of the initial roll out to OneDrive it currently looks like you will be migrated from July 2021.
Why make the change?
Once a recording is stored in OneDrive (or SharePoint) a large number of benefits are unlocked and these are listed on the web page I’ve highlighted above. To give you a taster I’ve put together the 2 minute video below, which shows how to add a retention label to a recording and how to share it with an external user. The nice thing about having recordings in OneDrive and SharePoint is that these files are managed by the same Microsoft 365 tools that you are already using for other content such as Office documents.
Note: At the time of this post there are some gaps, check out the roadmap. One thing you should be aware of is that it’s not currently possible to block the download of video files if they have been shared. A reference is provided here. If this is a problem you will probably need to review your meetings polices and SharePoint/OneDrive sharing permissions.
The following links provide a good source of additional information about “new” Stream: