Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

New-Team in PowerShell Runbook doesn't work since yesterday

%3CLINGO-SUB%20id%3D%22lingo-sub-2263811%22%20slang%3D%22en-US%22%3ENew-Team%20in%20PowerShell%20Runbook%20doesn't%20work%20since%20yesterday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2263811%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Esince%20yesterday%2C%20my%20PowerShell%20Runbook%20for%20Teams%20creation%20doesn't%20work%20anymore.%20It%20seems%20like%20the%20New-Team%20cmdlet%20is%20broken%20(%3CSPAN%3EMicrosoftTeams%20Module%20V1.0.1)%3C%2FSPAN%3E.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20get%20following%20error%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ETeam%20couldn't%20create.%20Error%20occurred%20while%20executing%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECode%3A%20NotFound%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EMessage%3A%20Failed%20to%20execute%20MS%20Graph%20backend%20request%20GetGroupInternalApiRequest.%20The%20server%20failed%20to%20respond%20correctly.%20Response%20Code%3A%20NotFound%2C%20Reason%3A%20Reason%3A%20Not%20Found%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20strange%20is%20that%20the%20SharePoint%20Site%20exists%20for%20a%20short%20time%2C%20but%20then%20gets%20automatically%20deleted.%3CBR%20%2F%3EI%20can%20then%20find%20the%20site%20in%20the%20SharePoint%20Admin%20Center%20under%20deleted%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20idea%20what%20this%20could%20be%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2263811%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2263881%22%20slang%3D%22en-US%22%3ERe%3A%20New-Team%20in%20PowerShell%20Runbook%20doesn't%20work%20since%20yesterday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2263881%22%20slang%3D%22en-US%22%3EShort%20update%3A%20A%20Microsoft%20365%20group%20is%20also%20created%20each%20time%20(and%20will%20be%20deleted%20directly).%20So%20it%20looks%20like%20the%20reason%20for%20the%20error%20is%20in%20the%20creation%20of%20the%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2267772%22%20slang%3D%22en-US%22%3ERe%3A%20New-Team%20in%20PowerShell%20Runbook%20doesn't%20work%20since%20yesterday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2267772%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EDo%20you%20have%20any%20update%20on%20this%3F%20I%20expierence%20the%20same%20issue..%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271838%22%20slang%3D%22en-US%22%3ERe%3A%20New-Team%20in%20PowerShell%20Runbook%20doesn't%20work%20since%20yesterday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271838%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1023567%22%20target%3D%22_blank%22%3E%40nielsdejager%3C%2FA%3E%26nbsp%3BNo%2C%20unfortunately%20not.%20I%20Hope%20someone%20can%20help%20us%20with%20the%20problem...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20had%20the%20problem%20for%20a%20longer%20while%20or%20just%20recently%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271855%22%20slang%3D%22en-US%22%3ERe%3A%20New-Team%20in%20PowerShell%20Runbook%20doesn't%20work%20since%20yesterday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271855%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1021592%22%20target%3D%22_blank%22%3E%40s9kelei%3C%2FA%3E%26nbsp%3Bjust%20recently%2C%20i%20am%20in%20talk%20with%20Microsoft%20support%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20testing%20we%20found%20out%20that%20it%20is%20working%20when%20the%20team%20has%20only%20one%20word%2C%20this%20is%20working%20for%20example%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3ENew-Team%20-MailNickname%20onewordteam%20-DisplayName%20%22onewordteam%22%20-Owner%20administrator%40tenantname.onmicrosoft.com%20-Visibility%20%22Public%22%20%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EAnd%20this%20is%20failing%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3ENew-Team%20-MailNickname%20twowordteam%20-DisplayName%20%22two%20wordteam%22%20-Owner%20administrator%40tenantname.onmicrosoft.com%20-Visibility%20%22Public%22%20%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

since yesterday, my PowerShell Runbook for Teams creation doesn't work anymore. It seems like the New-Team cmdlet is broken (MicrosoftTeams Module V1.0.1)

 

I get following error: 

 

Team couldn't create. Error occurred while executing

Code: NotFound

Message: Failed to execute MS Graph backend request GetGroupInternalApiRequest. The server failed to respond correctly. Response Code: NotFound, Reason: Reason: Not Found

 

What is strange is that the SharePoint Site exists for a short time, but then gets automatically deleted.
I can then find the site in the SharePoint Admin Center under deleted sites.

 

Does anyone have any idea what this could be?

 

Best regards

8 Replies
Short update: A Microsoft 365 group is also created each time (and will be deleted directly). So it looks like the reason for the error is in the creation of the team.
Hi,

Do you have any update on this? I expierence the same issue..

@nielsdejager No, unfortunately not. I Hope someone can help us with the problem...

 

Have you had the problem for a longer while or just recently?

@s9kelei just recently, i am in talk with Microsoft support now.

 

When testing we found out that it is working when the team has only one word, this is working for example;

New-Team -MailNickname onewordteam -DisplayName "onewordteam" -Owner administrator@tenantname.onmicrosoft.com -Visibility "Public" 

And this is failing;

New-Team -MailNickname twowordteam -DisplayName "two wordteam" -Owner administrator@tenantname.onmicrosoft.com -Visibility "Public" 

 

Ok that's nice to know, I'll try and give you an update.
Which version of The MicrosoftTeams Powershell Module do you use?

In my tests I have noticed that the teams creation does not fail 100% of the time. For example, on Monday I was able to create a team. But this worked only once. The DisplayName of the team had 4 words in this case. Maybe this is a useful information for the Microsoft support.
Unfortunately, the Teams creation doesn't work for me either if the DisplayName contains only one word...
Could you please give me an update here, when they find the reason for the problem?

@nielsdejager Have they solved your problem?

It is resolved today, the problems was reseolved in 2 steps;
1 - Microsoft support had to 'Refresh the sync', after microsoft support did something on the background it started working again from powershell

But i also faced the issue om Azure automation and before it worked there i had to update the Microsoft Teams powershell module.

So best approach for you would be to contact Microsoft support and ask for a 'Sync refresh'.

Good luck!