3 ms·

"I love how integrated it is but I had to write code to remove the integration that was counterproductive" I get it, but it seems contradictory, and your worka

"I love how integrated it is but I had to write code to remove the integration that was counterproductive" I get it, but it seems contradictory, and your workaround is probably beyond reach for many smaller businesses.

moksly 7y ago
I get your point, but I’m not sure you can apply enterprise problems to small businesses. Take my specific example, my department has a mailing list called something along the lines of Digitalisation, we have this because we’re 7000 employees at 200+ locations and you can be pretty sure a teacher at one of our schools don’t know who I am or what my position is called. They would know that they need to contact Digitalisation, so we have a mailing list for it, just like this particular school has a naming list with the schools name in case I needed to contact them. That wouldn’t really be an issue when you have 50 employees in the same office. Aside from that, I think Microsoft actually ended up adding a standard feature to hide Teams mail-addresses from the outlook addressbook when we raised the issue with Seattle, we just needed the extra “Teams -“ to make it easier to maintain.
- johnbatch 7y ago
  You can use a group naming policy to enforce your “Teams-“ prefix requirements [1]. Or you can use a custom domain policy so the email addresses are at “@teams.company.com” [2] 1.https://docs.microsoft.com/en-us/office365/admin/create-groups/groups-naming-policy?view=o365-worldwide https://docs.microsoft.com/en-us/office365/admin/create-grou... 2. https://docs.microsoft.com/en-us/office365/admin/create-groups/choose-domain-to-create-groups https://docs.microsoft.com/en-us/office365/admin/create-grou...
laurentb 7y ago
a simpler version of that workaround can be built with a powershell script (and hell, with a little bit of fiddling around, you can even use PowerApps as a front UI) in less than 2 days if not one morning.

moksly 7y ago

I get your point, but I’m not sure you can apply enterprise problems to small businesses. Take my specific example, my department has a mailing list called something along the lines of Digitalisation, we have this because we’re 7000 employees at 200+ locations and you can be pretty sure a teacher at one of our schools don’t know who I am or what my position is called. They would know that they need to contact Digitalisation, so we have a mailing list for it, just like this particular school has a naming list with the schools name in case I needed to contact them. That wouldn’t really be an issue when you have 50 employees in the same office. Aside from that, I think Microsoft actually ended up adding a standard feature to hide Teams mail-addresses from the outlook addressbook when we raised the issue with Seattle, we just needed the extra “Teams -“ to make it easier to maintain.

johnbatch 7y ago
You can use a group naming policy to enforce your “Teams-“ prefix requirements [1]. Or you can use a custom domain policy so the email addresses are at “@teams.company.com” [2] 1.https://docs.microsoft.com/en-us/office365/admin/create-groups/groups-naming-policy?view=o365-worldwide https://docs.microsoft.com/en-us/office365/admin/create-grou... 2. https://docs.microsoft.com/en-us/office365/admin/create-groups/choose-domain-to-create-groups https://docs.microsoft.com/en-us/office365/admin/create-grou...

laurentb 7y ago

a simpler version of that workaround can be built with a powershell script (and hell, with a little bit of fiddling around, you can even use PowerApps as a front UI) in less than 2 days if not one morning.