MS Teams issues

[Techie-Tech]

Good morning all,

We use Salamander Integration Suite via SDS for creating the Teams but have been having various issues with Teams over the last week or two. 

There seem to be a few glitches with Teams assignments. Some students and staff are getting error messages when trying to open assignments, and - most annoyingly - it is not currently letting you attach files to Teams assignments if those files are stored in the Cloud (either OneDrive or SharePoint).   We have also seen assignments set, and then disappear.

There is an open support ticket with MS for this and I have asked for it to be escalated, but this doesn't appear to be happening.

Has anyone else been having similar issues?

Thanks

 

[NegativeKillDeath]

Had a similar issue with our teams. They aren't bulk created by SDS and provisioned on demand by a Powershell script. Our script uses an old way of setting up the team and the "apps" class notebook, assignments etc weren't set with the correct permissions. I found the following script to fix them veltwerk/Repair-Class-teams at e1b6f0986c2ded9c0e2dbdfff5860fbb233e8487

 

 

[lparry]

2 hours ago, NegativeKillDeath said:

Had a similar issue with our teams. They aren't bulk created by SDS and provisioned on demand by a Powershell script. Our script uses an old way of setting up the team and the "apps" class notebook, assignments etc weren't set with the correct permissions. I found the following script to fix them veltwerk/Repair-Class-teams at e1b6f0986c2ded9c0e2dbdfff5860fbb233e8487

 

 

 

Exactly this - we had very similar issues due to the way provisioning changed. I believe SalamanderSoft have a script to fix already deployed teams and Microsoft can provide one as well (I'd try and get ours but my colleague dealt with it and he is on annual leave)

 

Looking at the linked script though - they all look like they do pretty much exactly the same fix of changing permissions of the edu apps so I'd suspect this one would work as well

[CyBeRkId2002]

Yes - the above definitely fixes things and was something we needed to do a couple of weeks back.

 

Out of interest, does anyone know the correct way to provision using powershell these days to avoid this issue?

[lparry]

1 hour ago, CyBeRkId2002 said:

Yes - the above definitely fixes things and was something we needed to do a couple of weeks back.

 

Out of interest, does anyone know the correct way to provision using powershell these days to avoid this issue?

 

This is what I bookmarked when I was researching it initially which seems to document the changes:

------------------------------------------

We encountered the same issue when creating Teams. The Notebook app fails to launch, and it seems something has changed on Microsoft's side regarding how Teams are provisioned.

Previously, we created a group first and then promoted it to a Team using an Edu_C template. However, when we now create a new Team this way, the Notebook throws an error.

Old Method (Group → Team)

# Create Group
$params = @{
    displayName = $name
    mailNickname = $name
    description = $name
    groupTypes = @("Unified")
    mailEnabled = $true
    securityEnabled = $false
    visibility = "HiddenMembership"
    creationOptions = @("ExchangeProvisioningFlags:461", "classAssignments")
    extension_fe2174665583431c953114ff7268b7b3_Education_ObjectType = "Section"
}

# $Newgroup = New-MgGroup -BodyParameter $params
$groupResponse  = Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/groups" -Body $params
$groupId = $groupResponse.id

New Working Method (Create Class → Promote to Team)

Instead of creating a group first, you now need to create an Education Class. Once you promote this class to a Team, the Notebook works correctly

# Payload for education class
$params = @{
    displayName     = $name
    mailNickname    = $name
    description     = "$name class group"
    classCode       = "BIO101"
    externalId      = "BIO101-3558"
    externalName    = $name
    externalSource  = "sis"
} | ConvertTo-Json -Depth 10

# Call to beta endpoint
$groupResponse = Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/beta/education/classes" -Body $params

-------------------------

 

Which does match up to what is mentioned by microsoft:

Quote

Note:

This will also create a universal group. When you use this API to create a class, it will add special properties to the group, which will add features such as assignments and special handling within Microsoft Teams when teams are created using the group. Please note that this API only creates the universal group and does not create a team. Microsoft Teams provides a user interface for teachers to create teams for their own classes using the groups created by this API.

 

[NegativeKillDeath]

If you use the MicrosoftTeams powershell module 7.3.1 and the New-Team command with the -Template 'EDU_Class' it works. 

 

The 7.3.1 version is less than a month old which was our issue as we weren't aware of it so didn't call it. 

 

Provisioning classes at scale using PowerShell and Microsoft Graph - Microsoft Support

[Techie-Tech]

5 hours ago, NegativeKillDeath said:

Had a similar issue with our teams. They aren't bulk created by SDS and provisioned on demand by a Powershell script. Our script uses an old way of setting up the team and the "apps" class notebook, assignments etc weren't set with the correct permissions. I found the following script to fix them veltwerk/Repair-Class-teams at e1b6f0986c2ded9c0e2dbdfff5860fbb233e8487

 

 

Hi there,

Did you just run this across all the Team sites of did you only pic the ones that were being flagged up?

Thanks

[NegativeKillDeath]

Just now, Techie-Tech said:

Hi there,

Did you just run this across all the Team sites of did you only pic the ones that were being flagged up?

Thanks

 

Just the ones that were created since middle of August. We don't typically use Teams here but teachers can request it for their classes so I only had about 20 to do.