SOLVED

New Microsoft Teams not creating Outlook Mailbox anymore?

Copper Contributor

Hey guys,

 

We've got this issue in our tenant (and also in our Test & Dev Tenants) where since (around) this last Friday the 8th Dec, new Microsoft Teams do not create an Outlook / Exchange Mailbox anymore.

 

When we create new a Team, a new SharePoint Site or also simply a new M365 Groups, they don't automatically create an Outlook / Exchange Mailbox...

 

For example, this new M365 Group only created a SharePoint Site and a Team, but no Mailbox.

casparrubin_0-1702231151988.png

 

 

Before Friday, we always automatically got a mailbox:

casparrubin_1-1702231155928.png

 

 


There is nothing different in how we create the Teams... we have mailbox enabled in our scripts.

 

But this also happens if we create Teams manually via the Admin Center. Or create a new Team Site in the SharePoint Admin Center. Or simply create a new M365 Group in Azure / Entra ID...

 

Anyone know how this can happen?

 

Any help or insight is greatly appreciated!

 

Cheers

5 Replies
When you create a Microsoft Teams team, a corresponding Microsoft 365 group is created. This Microsoft 365 Group includes various features, such as a shared inbox, oneNote notebook, and a SharePoint site.
The shared inbox which is essentially an email address can be used for communication within the team. However automatic creation of a standalone mailbox(Independent of the share inbox within the Microsoft 365 Group) When creating a new team in Microsoft Teams Isn't a built-in feature.

If you specifically need a separate mailbox created upon the creation of a new team, you may have to create an additional mailbox through Microsoft 365 admin.
This process involves administrative access and configuration within the Microsoft 365 environment.

Hey @NnekaEne_2023, thanks for the reply.

 

[...] This Microsoft 365 Group includes various features, such as a shared inbox, oneNote notebook, and a SharePoint site. [...]

 

That's what I mean, it's not creating the shared inbox anymore for us. It does not matter how we create the Team. A private Team should always create a shared Inbox but it's not doing that anymore since last Friday. We have around 4k Teams in our Tenant and it just stopped creating inboxes this last Friday.

 

@casparrubin I think first question here is are you missing the shared mailbox? If not and all is functioning fine don't bother if Yes create a ticket.

 

 

If I have answered your question, please mark your post as Solved

If you like my response, please give it a LikeLikeLike

visit my youtube channel KbWorks! :smile: or KbWorks.eu

It seems to be a problem due to EX697203. 

https://support.nhs.net/2023/12/microsoft-365-alert-service-degradation-exchange-online-some-users-m...

 

I will change the command to create.

 

Error

New-Team -DisplayName $displayname -MailNickName $alias -Visibility "Private"
 
Success
$a = New-UnifiedGroup -DisplayName $displayname -Alias $alias -AccessType Private -PrimarySmtpAddress $emailadress
New-Team -GroupId $a.ExternalDirectoryObjectId
 

 

 

 

@casparrubin 

best response confirmed by casparrubin (Copper Contributor)
Solution

Microsoft updated their active issue report yesterday with the following:

[...] When creating a new Group via Microsoft Teams, the Group will show as being created, but it may not be correctly created. [...]

 

and

 

 [...] we've determined that our earlier reported impact didn't accurately represent the entire impact scenario [...]

 

https://portal.office.com/Adminportal/Home?#/servicehealth/:/alerts/MO697570

casparrubin_0-1702461179088.png

 

I looks like I'll just have to wait for them to fix it. Thank you everyone.

1 best response

Accepted Solutions
best response confirmed by casparrubin (Copper Contributor)
Solution

Microsoft updated their active issue report yesterday with the following:

[...] When creating a new Group via Microsoft Teams, the Group will show as being created, but it may not be correctly created. [...]

 

and

 

 [...] we've determined that our earlier reported impact didn't accurately represent the entire impact scenario [...]

 

https://portal.office.com/Adminportal/Home?#/servicehealth/:/alerts/MO697570

casparrubin_0-1702461179088.png

 

I looks like I'll just have to wait for them to fix it. Thank you everyone.

View solution in original post