Admin of multiple Teams sites

[petben]

Our subject departments will start using Teams for files storage and to send emails to department colleagues. IT will need to access all their Teams files, provide support etc, so how do you manage that without being inundated with everyone’s emails? Are IT Owners of the all the Teams and then each Team has all the communications turned off for that IT user, or is there a simpler way?

 

To clarify - staff will be using outlook to send emails to the Team members, so as an IT admin I don’t want to receive those emails..

Edited November 29, 2023 by petben

[HPlum78]

My first thought is why you think that you need to be in the team(s) at all? Would like to see your service wrapper for this before I could comment any further.

[kennysarmy]

My first thought is why you think that you need to be in the team(s) at all? Would like to see your service wrapper for this before I could comment any further.

 

I support my colleagues use of Teams without being in ANY of their Teams

[Boredguy]

We have a dedicated account for creating the Teams and use that as one of the Owners, so that it doesn't clutter up our own mailboxes, and means if we need to assist staff with accessing resources within the Team it's reasonable quick to open a new browser session with those credentials, without hunting for the right team in the admin console (as we have over 500 teams) then adding the account, then accessing Teams to help.

[DaveTheTech]

Its all fairly hands off at this point.

But in the past I have just added myself to a Team.

Connect-MicrosoftTeams
$staff = Get-ADUser -SearchBase "DC=Domain, DC=Lan" -filter {enabled -eq $true} | sort name$copyFROM = $staff | ogv -PassThru -Title FROM$copyTO = $staff | ogv -PassThru -Title TO
$existingUser = get-team -User $copyFROM.UserPrincipalName -Archived $false
$newTeam = $existingUser | sort DisplayName | ogv -PassThru$newTeam | %{

[indent]if($_.MailNickName -like "Section_*"){[/indent]


[indent=2]$role = "Owner"[/indent]


[indent]}else{[/indent]


[indent=2]$role = "Member"[/indent]


[indent]}

[/indent]




[indent]write-host adding user to $_.DisplayName as a $role    [/indent]




[indent]Add-TeamUser -GroupId $_.GroupID -User $copyTO.UserPrincipalName -Role $role[/indent]




[indent]}[/indent]


}

 

The "Section_" is a dirty way of selecting SDS created Teams.

Staff need to be an owner of those groups. Else they can just be members.

Edited November 29, 2023 by DaveTheTech

[localzuk]

I only add myself to a team when an issue is brought up. Otherwise, I'm only in the teams relevant to me. Can't see a reason to be in them all the time.

[petben]

We have a dedicated account for creating the Teams and use that as one of the Owners, so that it doesn't clutter up our own mailboxes, and means if we need to assist staff with accessing resources within the Team it's reasonable quick to open a new browser session with those credentials, without hunting for the right team in the admin console (as we have over 500 teams) then adding the account, then accessing Teams to help.

 

 

I think for us this seems the most attractive, so we would create a teamsadmin account (no mailbox), add that as owner of all teams and use that on the odd occasion we need to investigate lost files or something?

 

yes, it was also a fair comment why we need this access at all, we dont really know what questions/tasks will come up.