Forum Discussion
Mandatory audience targeting before publishing news
Hi PerHardafSegerstad I have checked your case and observed different behavior on the Teams site compared to the Communication site. Using exactly your approach, I was able to achieve the desired result on the Communication site. Could you confirm whether you are using a Teams site in your case? If so, this seems like a good case for an incident ticket to Microsoft.
Hi michalkornet and thank you for your reply! Sorry for not including site type in my original question. I am indeed using a Teams site, so based on your findings it looks like we've found a discrepancy between how the two types of sites are handling this. I will report it to Microsoft and hope for the best. Thank you again!
PerHardafSegerstad - we are running into the same challenge at our org, were you able to work with Microsoft on the resolution for this?
MyNameIsJeff - not directly with Microsoft, but after discussions and testing with our local MS partner I think we might have a solution. We have not implemented it in production yet, but it works in our test environment so we will try it soon.
Here's the plan: locally in the Site Pages library and on the Events list (to make target audience obligatory for events as well as for pages/news) we will set Target Audience to Obligatory for the content types related to news posts, pages, redirect pages and events. For events we also need to set the column as obligatory in the modern interface. Just setting the column as obligatory doesn't work for us, probably because we're using Teams sites and not Communication sites (see michalkornet's findings earlier in this thread).
The reason we're doing it in the library and on the list, and not sitewide, is that since we're changing the standard content types it might have consequences we haven't thought of somewhere down the line. So, the con here is if Microsoft does anything with the standard content types we run the risk of having to make our change again. The pro is, hey, it works! Hopefully. We're going live with this September 9, I can report back after that.
(We've considered using custom content types, and I would prefer that, if it wasn't for the small detail that we can't add those to the "+ New" button on the site start page. And right now I can't be bothered with teaching all our 200+ editors a new way of creating news and pages. 😊)
