Audience Targeting for News not working at Hub Site level

Copper Contributor

We have a Hub site and are pulling in news from sites associated with the Hub.  I have set targeted audiences on those news articles and have tested the functionality on the sites themselves - the audience targeting seems to work fine.  However, at the hub site level, pulling the news from those sites into a news web part, when I enable the audience targeting feature, no action is taken.  It doesn't appear the audience targeting functionality is working in this scenario. Is this expected behavior?

25 Replies
When you enable the option on the web part, you have to give it 10-15 minutes since it runs off search to update the search index for the users, but that is all there is too it. Make sure the audiences you are assigning, do not have the person logged in for the test in them as well obviously :p

@Pam DeLung I am having this issue as well. I have waited as long as a 24 hour period and still the same result.

Laura Rogers just did a power hour over this and it was working. I’ll need to go test it out and see if something has broke or not.

@TrippMD  - Same here.  We put this in place over 24 hours ago, still not working. 

@Chris Webb - Yes!  I watched Laura's Power Hour on the audience targeting, but I can't remember if she covered this scenario.  It works perfect on same site testing for us.  It's the rolling up of news to hub site level - that's where we're seeing the issue of the audience targeting not working successfully.

Are you missing news, or is it just showing all news?

@Chris Webb It works fine for same site but it shows all the news at HUB site.

@Chris Webb - It's showing all news.

@Chris Webb - Hey there.  Wondering if you'd had a chance to test this in your tenant and if so, what was your experience?

Hi Pam, having the same experience, did you have any joy with this? @Pam DeLung 

We have the same issue. Has anyone been able to find if this is a bug, or just not supported by SharePoint Online?



I managed to figure out the issue, you need to ensure the following for it to work correctly.

1. ensure you have audience target enabled on sitepages of the actual site, and that you enable audience targetting on the news webpart, then verify its actually working correctly.

2. Then go to the hub site, and do the same, enable on the sitepages of the hub and enable on the news webpart.


In short you need to have audience target enabled on hub and on site for the news rollup to work not just on the hub. Hope this helps.


Hi everyone.

One customer has the same problem. The audience is set in the Site Pages and in News webpart on both -  the Hub site and the associated site. Targeting works fine on the associated site. No news that has a target audience set in the source site (associated with the hub site) will be displayed on the Hub site News web part.


Does anyone have any ideas what this could be? I'm getting frustrated with that.

Thank you.


@Lenkaa - Hi there!  Something that may seem small, make sure the news article that you added the target audience has been published to a major version.  

Hi @Pam DeLung,
thank you for your reply and help. Bu yes, they are all in the major version. This is a general problem when I view news using the Select site or All sites in the hub option. When I turn off audience targeting in the News webpart, I see all the news from other sites. However, when I turn on this feature, only those that do not have any groups filled in the Audience column will remain displayed.
It looks like SharePoint can't tell if I'm a member of an embedded group or not. But the This site option works with targeting without any problems and displays the news where I'm a member of the group.

I have same problem, did you find any solution for this issue?
seems like the problem not solved, we still got the problem,
it works from A to B to publish news, but if we do it from B to A
then it only work for the first Security group added in Targeting

From memory this audience target feature does have some limitations on what it can use. Ill try and find the blog post but from memory you can't use 1 type of group and nesting can be an issue if your not a direct member of the actual group, i do know that dynamic groups and synced onpremise security groups to Azure AD do work.
Since this post i think Dynamic groups do infact work now.

Azure Active Directory groups (including security groups and Microsoft 365 groups) are supported with the exception of AAD dynamic groups. AAD dynamic groups will be supported some time in 2021.