Zuntara

TEAMS MEETING RECORDINGS

All Teams recordings are now stored in OneDrive for Business and SharePoint.

Note: If a Teams meeting recording fails to successfully upload to OneDrive or SharePoint, “The recording ended unexpectedly” error message will appear in the meeting chat, and the recording will instead be temporarily saved to Azure Media Services (AMS). Once stored in AMS, no retry attempts are made to automatically upload the recording to OneDrive/SharePoint or Stream. It will stay in AMS for only 21 days and is automatically deleted after that.

Where are meeting recording stored?

For general Teams meetings, the recordings are stored in a folder called Recordings on the root level of the OneDrive of the person who starts the meeting recording.

For Channel meetings, the recordings are stored in the Teams site document library in a folder called Recordings.

By default, all recording files stay on the OneDrive of the user who starts the recording. For channel meetings, the recording will always go to the SharePoint site of the channel. Admin cannot change where the recording is stored.

How to manage recording of former employees?

Videos are just like any other file in OneDrive for Business and SharePoint. Managing ownership and retention after an employee leaves the company will follow the normal OneDrive for Business and SharePoint process.

Who has permission to view the meeting recording?

For general meetings, all meeting invitees, except for external users, will automatically get a shared link. External users will need to be explicitly added to the shared list by the meeting organizer or the person who started the meeting recording.

For Channel meetings, permissions are inherited from the owners and members list in the channel.

Note: You’ll not receive an email when the recording is saved, but the recording will appear in the meeting chat once it is saved.

How to manage captions?

At the time of recording closed captions will be available during playback only if the user had transcription turned on. Admins must turn on recording transcription to ensure their users have the option to record meetings with transcription.

Closed captions are supported for Teams meeting recordings for 60 days from when the meeting is recorded.

Closed captions are not fully supported if the Teams Meeting Recording is moved or copied from its original location on OneDrive for Business or SharePoint.

 Note: There will be English-only closed captions.

How is my storage quota impacted?

Teams meeting recordings are considered like any other files and are included in your tenant quota. See SharePoint quota and OneDrive for Business quota.

What happens is user does not have OneDrive or SharePoint, or the storage quota is full?

The recording will go to temporary storage location and stay for 21 days. The meeting organizer can download the recording during that time. If not downloaded within 21 days, the recording is deleted.

Get Microsoft Purview Information Protection Labels from Tenant.

Microsoft Purview Information Protection or Sensitivity Labels are a way to classify documents (files, emails, pictures) and containers (Sites & Teams) in a tenant. MPIP Labels can help safeguard important information in a company.

What do you need?

Information protection role. Either RBAC or system roles.
Exchange Online Module.

How to get all the labels and label policies in a tenant.

$output = "c:\temp\miplabels.csv"

Set-ExecutionPolicy -ExecutionPolicy Unrestricted

Connect-IPPSSession -UserPrincipalName "youruserprinciplename@contosco.com"

$labels = Get-Label

foreach ($label in $labels) {

$policies = Get-LabelPolicy -WarningAction Ignore | ? {$_.ScopedLabels.GUID -eq $label.Guid}

        
if ($policies) {
            
foreach ($policy in $policies) {

$string = $label.DisplayName + "," + $policy.Name + "," +  $label.CreatedBy + "," + $label.WhenCreated + "," + $policy.ModernGroupLocation + ',' + $policy.CreatedBy + ',' + $policy.WhenCreated

Write-Host $string`r`n`r`n
Add-Content $output $string
}
                
elseif ($label.Guid.Guid -ne $policy.ScopedLabels.Guid) {
$string= $label.DisplayName + "," + "" + "," +  $label.CreatedBy + "," + $label.WhenCreated + "," + "" + ',' + "" + ',' + ""
                
Write-Host $string `r`n`r`n
Add-Content $output $string
  }
}

Disconnect-ExchangeOnline

Add selected sites API permissions to Azure app.

What do you need?

Azure app id of a registered app where you add selected sites API.
Azure app name of a registered app where you add selected sites API.
SharePoint site(s).
Primary Azure app id.
Primary Azure app certificate.

$domain = "Contosco.onmicrosoft.com"
$primaryAppId = "Your primary app id."
$primaryAppCertificateThumbprint = "Your primary app certificate."
$adminCenterURL = "You SharePoint admin center URL."

$selectedSiteAppId = "App id of Azure app where you add selected sites API."
$selectedSiteAppName = "App name of Azure app where you add selected sites API."

$selectedSiteURL = "https://sharepoint.contosco.com/sites/marketing"

Connect-PnPOnline -Url $adminCenterURL -Tenant $domain -ClientId $primaryAppId -Thumbprint $primaryAppCertificateThumbprint -WarningAction Ignore

# you can grant read or write
Grant-PnPAzureADAppSitePermission -AppId $selectedSiteAppId -DisplayName $selectedSiteAppName -Site $selectedSiteURL -Permissions Write

M365 Ownerless Groups

A M365 group becomes ownerless when the last owner of the group account is deactivated/disabled. Normally this happens when someone leaves the company. As a best practice a group should always have more than 1 owner to manage the groups. A M365 group can be created when creating a Viva Engage community, a Teams, a Planner, or an Outlook group.

Microsoft has made it easier by automating group ownership assignment using setting from M365 admin center: M365 admin portal > Settings > Org Settings > Microsoft 365 Groups > Under Ownerless groups check the box When there’s no owner, email and ask active group members to become an owner.

You can configure different settings based on your needs. Once the settings are set, active members of the ownerless groups will receive email. Members can choose to be owners without leaving email. Once 2 members take ownership, it will not allow other members to be an owner. This setting can help clean up orphaned groups and govern data by managing group.

AutoSave In Depth – How to control AutoSave.

AutoSave is available on all M365 office files with a subscription that saves your files without having to save the files manually.

AutoSave goes hand in hand with versioning. Make sure versioning is turned on the library where the files are stored.

Note: Office app will not save automatically every few seconds If you turn off AutoSave and therefore there is a chance that users may not see each other changes.

You can control Autosave using:

Group policies.
Office Apps Admin center using cloud policies.
Manually for each Office files. File > Options > Save > AutoSave files stored in the Cloud by default in Word
Using AutoSave toggle from the top of Office file. It will remember the last manual toggle setting for that specific file when you reopen.

Control OneDrive for Business Settings Using Group Policy.

Control OneDrive for Business Settings Using Group Policy.You can control many settings using OneDrive for business group policy. Some of the popular and important one is known folder move where you can back up your Desktop, Documents, and Pictures folder on your computer to the cloud. Other settings you can control are Files on Demand, Updating OneDrive, automatically signing in to OneDrive etc.

What are the steps you need to take to go from zero to enabling group policy in an organization? Below are the steps:

Getting things ready.

Make sure your user account that logs into the company computer is Azure AD or hybrid joined.
OneDrive now comes with Windows image, so it is not necessary to install separately.
To manage Group policy in OneDrive for business you need administrative template (.admx file), and Language file (.adml file). Without these you will not see any OneDrive settings in the group policy editor.
Install the most recent OneDrive sync client in Windows device.
Copy the two files from below path: C:\Users\youruserid\AppData\Local\Microsoft\OneDrive\latestOneDriveVersion\adm
If you want certain language instead of English, use that one from inside the adm/languagefolder instead from the adm root folder.
Copy two files to Group Policy central store like: \\FDQN\sysvol\FDQN\Policies\Policy Definations\
The admx file goes to the root, and adml file goes to the language folder.
You are now ready to create OneDrive group policy object.
Create a new GPO and name it something like OneDrive Settings: For GPO containing computer configurations you can link this policy to an organization unit containing your windows devices or link it to a domain and filter the GPO for windows 10 devices or security groups. The same goes for user configuration settings. Whether you use an organizational unit, WMI filtering, or security filtering depends on the design of your directory.
Edit the GPO, and on Computer Configuration, Open Policies folder > Administrative Templates (Administrative Templates Policy definitions), OneDrive.
From here you should be able to all OneDrive settings through policies.

Move to Copy to Feature in SharePoint, OneDrive & Teams.

You can move or copy files and folders from one SharePoint site to another, one Teams to another, or from OneDrive to SharePoint or Teams and vice versa.

Move to and Copy can be found from the menu from each file or from the ribbon of each document library page.

Things to remember:

Make sure the destination document library does not have unique values enforced on the primary column.
DO NOT refresh the page or navigate away from the page while copying or moving.
Make sure each file is less than 2 GB.
DO NOT move or copy more than 100 GB total file size.
Copying files and folders will only copy the newest version of the file and folders. Custom Metadata columns will not be copied if custom metadata columns are not already created in the destination.
DO NOT move or copy more than 30,000 files.
If moving and if the metadata columns do not exist in the destination, create metadata columns first in the destination to match the source metadata column.

Stop SharePoint Workflow Tenant Wide

Classic SharePoint workflows (2010 & 2013) are no longer supported in M365. You may want to stop it before users create more workflows.

Starting August 1st, 2020, SharePoint 2010 workflows are turned off for any newly created tenants.

Starting November 1st, 2020, SharePoint 2010 workflow services are removed from existing tenants so that no new or existing 2010 workflows will run. 

The following built-in workflows will be impacted:

Approvals, collect feedback, collect signatures, Classic pages publishing approval, Three-state, and Disposition approval.
SharePoint server still supports both SharePoint 2010 and 2013 Workflows.
SharePoint Designer 2013: SharePoint 2010 workflow creation and execution against SharePoint Online from SharePoint Designer 2013 is turned off for any newly created tenants starting August 2020 and existing tenants starting November 2020. Existing workflows can only be viewed as raw XML files. 
SharePoint Designer 2013 will work with SharePoint Server 2019 for the remainder of the client support lifecycle (2026). SharePoint Designer 2013 will not be supported beyond that timeframe.
User interface updates when SharePoint 2010 workflows is disabled on a tenant.

We can stop creation of new SharePoint 2010 & SharePoint 2013 Workflows using new PowerShell commands below:

# Set to true to stop 2010 WF 
Set-SPOTenant -StopNew2010Workflows $true 


# Set to true to stop 2013 WF 
Set-SPOTenant -StopNew2013Workflows $true

The already created workflows will not be affected and will continue to run.

After stopping creation of new SharePoint 2010 & SharePoint 2013 Workflows, if anyone tries to use SharePoint designer to create new workflows then they will get an error “The SharePoint admin has disabled the creation of new workflows. Existing workflows will continue to run “.

You may see below error when you try to publish the workflow.