I suggest you ....

News Web Part needs to have a Begin/Expiration date

The News web part should have the option to have a begin as well as an expiration date for the news posting in the modern experience, similar to the announcements with classic. The functionality should also extend to news posts aggregated within the Hub site. Currently, the only option to remove a news post is to either unpublish or delete the page from the source site's Site Pages library.

Site owners can organize news posts for placement in news web parts today. This capability was added to meet the need of “pushing” older content to the top, or ensuring a particular news post stays in place while other news posts automatically feed into the system. This works in all layouts, and news source configurations. We’re working on scheduling posts/pages for publication right now, but it likely won’t include an “expiration” date at launch as newer content naturally pushes out older content (that isn’t placed in a specific news slot). If this doesn’t meet your needs, we’d love to better understand the scenarios that require expiration dates. Thanks

Thank you for the feedback and update. The request to expire a news posting is for the ones that are no longer needed after a determined amount of time. We understand that the new postings will go to the top and that we can limit the number of news postings to be displayed. However, for certain postings especially that are time dependent or possible for those who may not post as frequent, we would like the ability for the news posting without having to delete or unpublish the page. With our business scenario, we have multiple news web parts from different sites rolled onto one in the HUB site and users can display these news postings for a set amount of time before the news is no longer needed to be displayed.