SOLVED

Update policies

%3CLINGO-SUB%20id%3D%22lingo-sub-2663641%22%20slang%3D%22en-US%22%3EUpdate%20policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2663641%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20guys%2C%20today%20I%20reviewed%20the%20update%20policies%20in%20the%20teams%20admin%20center.%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20I%20searched%20for%20the%20documentation%20about%20this%20topic%20which%20I%20found%20here%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fmicrosoftteams%2Fpublic-preview-doc-updates%3FWT.mc_id%3DTeamsAdminCenterCSH%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPublic%20preview%20in%20Microsoft%20Teams%20-%20Microsoft%20Teams%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20what%20I%20found%20out%20is%20-%20that%20if%20you%20set%20in%20the%20tenant%20settings%20%26gt%3B%20release%20preferences%20%26gt%3B%20targeted%20release%20for%20selected%20user%20-%20the%20setting%20in%20the%20teams%20admin%20center%20do%20not%20overwrite%20the%20release%20preferences.%20Which%20means%20%22tenant%20%26gt%3B%20teams%22%2C%20right%3F%20I%20think%20this%20is%20confusing%20for%20some%20people%2C%20also%20nothing%20about%20that%20is%20in%20the%20documentation.%20So%20I%20think%20there%20should%20be%20a%20information%20about%20that%20in%20the%20documentation%20at%20least.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2663641%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2663700%22%20slang%3D%22en-US%22%3ERe%3A%20Update%20policies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2663700%22%20slang%3D%22en-US%22%3EHello%2C%20targeted%20release%20is%20something%20else%20in%20which%20Teams%20isn't%20included.%20To%20enable%20Public%20preview%20you%20have%20to%20follow%20the%20steps%20in%20the%20link%20you%20attached.%20If%20you%20look%20in%20PowerShell%20there's%20still%20AllowPreview%20(being%20deprecated)%20and%20the%20new%20AllowPublicPreview%20with%20the%20new%20settings.%20I%20think%20this%20is%20a%20bit%20buggy%20because%20the%20two%20parameters%20are%20in%20coexistence.%20I%20had%20to%20enable%20AllowPreview%20even%20though%20all%20was%20set%20up%20properly%20for%20AllowPublicPreview.%20But%20your%20scenario%20might%20be%20different%20than%20mine%20so%20you%20have%20to%20decide%20if%20you'd%20like%20to%20follow%20Office%20preview%20or%20just%20have%20the%20setting%20as%20enabled.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hey guys, today I reviewed the update policies in the teams admin center. 

Also I searched for the documentation about this topic which I found here: 

Public preview in Microsoft Teams - Microsoft Teams | Microsoft Docs

 

But what I found out is - that if you set in the tenant settings > release preferences > targeted release for selected user - the setting in the teams admin center do not overwrite the release preferences. Which means "tenant > teams", right? I think this is confusing for some people, also nothing about that is in the documentation. So I think there should be a information about that in the documentation at least. 

3 Replies
best response confirmed by Juan Carlos González Martín (MVP)
Solution
Hello, targeted release is something else in which Teams isn't included. To enable Public preview you have to follow the steps in the link you attached. If you look in PowerShell there's still AllowPreview (being deprecated) and the new AllowPublicPreview with the new settings. I think this is a bit buggy because the two parameters are in coexistence. I had to enable AllowPreview even though all was set up properly for AllowPublicPreview. But your scenario might be different than mine so you have to decide if you'd like to follow Office preview or just have the setting as enabled.

Thats a really good information - because personally I think it is a little bit confusing, also for customers - they think the setting is set in the org setting and do not pay attention to the update policies inside of microsoft teams.

Agree, it is a bit confusing, as most things are in Teams (referring to the massive amount of features being released). That's why we are here too :)
www.000webhost.com