Restoring teams with canals in one go: is it possible?

[Sam31Tls]

Hello VBM gurus!
i am trying to understand if the behavior i observe is by design,a bug, a misconfiguration or a misuse....

We have a "Test team" with a single canal nammed "default" with a single file in it
Try 1 :
we delete "Test team" , we restore "Test team" entirely with the teams explorer

• success of the restore but with information saying canal default skipped
  and indeed in teams application the canal is missing while a new, empty "General" canal as been created

Try 2:
we delete "Test team" , we restore "Test team" entirely with the teams explorer, then we make another restore of only the canal defaut

• this time the default canal appears in teams application
  but it took a two time restoration process

Is this a normal behaviour?
thank for your help!

[Polina]

Hi Sam31Tls,

That's indeed by design. A General channel is created by default each time you create a new team. When restoring an entire team, we re-recreate it from cratch and hence it gets a brand-new default General channel. The backed-up General channel has to be re-added as new custom channel.

[Sam31Tls]

We went further into our investigation on a lab and we could reproduce the issue. The details bellow but bottom line : it happens when the "initial canal" is not named "General" but with a custom name!
Our tests have shown:
- That restoring a Teams whose initial channel is named General works well (expected behavior).
- That restoring a Teams whose initial channel doesn't have this default name but another one ("default" in your case) causes the creation of a new initial channel named "General," and the old one must then be restored manually.
Note that if there are other, non-"initial" channels, they are correctly restored.
- That it is possible to rename an initial channel named "default" to General on a production Teams, save it, and then it restores correctly.
However, you may notice that during the restore, the old name still appears in the Teams Explorer console, most likely a cosmetic bug.

This behavior observed seems therefore "normal", although not satisfactory for our custimer, especially considering that the option to change the name of a Teams' initial channel is about a year old at O365.
So if anyone knows of another solution than those listed above, or if this functionnalty is maybe planned to be fixed our customer would be delighted, and probably some others .

Thank you advance for your help and insight on this matter!