This all sounds like an administrative nightmare. Using MSfB to curate a list of apps that our users are allowed to install, and then blocking the rest of the public store was the ideal solution for us. Now based on "feedback" you're taking away this simplicity to make our lives more complicated and taking more time away from admins. Typical Microsoft.
First, you say these new capabilities will not become generally available until H2 of 2022. Knowing Microsoft as we do, that likely means the back end of H2 at the earliest. MSfB is going away in Q1 2023. That doesn't give much time to get all of our store apps re-packed and published via another method.
Can I not just check a load of apps on a list from the public store and have them listed in company portal or SCCM software enter, while blocking the actual Store app? That would give me what I have now with minimal additional effort.
Secondly, as a store app, how exactly do I package and pre-deploy the company portal app to devices if the store is blocked?
Also if the store is blocked entirely in this new world (what company in their right mind would let employees have access to the whole Microsoft Store?) will inbox apps still update?
A total mess Microsoft, not happy at all.