Mario hi & and thx for asking here at Q&A platform ))))
actually this is a common licensing puzzle when you want to scale up github advanced security )) you are right, the bundled plan can be limiting when you only need specific features.
the transition from a bundled plan to a standalone plan is not something you can do yourself in the devops admin center. this is a billing operation that requires help from the microsoft commerce team.
first, you or your azure subscription admin needs to contact azure billing support directly. they are the only ones who can make this change on the backend. you can create a support request through the azure portal https://aka.ms/azsupt.
when you create the ticket, choose the 'billing' category. then, explain clearly that you want to migrate your existing 'github advanced security for azure devops' subscription from the bundled plan to the standalone plan. mention that you want to specifically use the code scanning and dependency scanning features, which is why you need the standalone sku.
it is also a good idea to cancel the current bundled subscription after you have confirmed the new standalone plan is active and assigned to your users. you do not want to have a gap in service. the billing support team can guide you on the exact timing for this to avoid being double charged.
once the standalone plan is active in your tenant, you will go back to your azure devops organization settings. in the 'billing' section, you should then see the option to assign the 'advanced security' standalone license to your users. you can then assign it to the specific committers who need it.
this process of changing a subscription sku is common across many microsoft cloud services. the path is always to go through billing support for these types of changes.
your main action is to contact azure billing support and request a migration from the bundled to the standalone github advanced security plan. they will handle the backend switch for you.
rgds,
Alex