Current process for independent developers to obtain Minecraft API / Xbox Live authentication access for a public launcher

Hello,

I am an independent developer currently building (removed by Moderator), a custom desktop launcher for Minecraft designed to offer the community an alternative user experience.

My goal is to ensure the project is 100% legal and compliant, requiring users to securely log in using their own legitimate Microsoft/Minecraft accounts via OAuth2 (using a native redirect URI for public clients: https://login.microsoftonline.com/common/oauth2/nativeclient).

However, I have noticed that older documentation and access request forms (such as aka.ms/UpgradeMinecraftAccessRequest) are outdated or no longer functional, and that standard application registrations in Azure encounter blocks related to client permissions for public authentication flows linked to Minecraft services.

Could you clarify the current official procedure or pathway for independent developers to request or correctly configure permissions to authenticate Minecraft players within a public desktop application?

I would greatly appreciate any updated documentation, guidelines, or points of contact regarding this matter; I simply want to be able to create this project—it is my first one, and it would be great to get the go-ahead.