Hi @NiklasWasserhe-2959 , can you please clarify a few things for me?
How is the app configured? Is it a multi-tenant or single-tenant app?
User accessing- is this user accessing the app from outside the tenant, are they within the tenant where the app is registered?
Depending on this, the app will behave differently. Implications of the publisher domain on the consent experience drawing from this documentation suggests that in the event a multi-tenant application's publisher domain isn't set, or if it's set to a domain that ends in .onmicrosoft.com, the app's consent prompt will show unverified in place of the publisher domain. This is as opposed to a single tenant app as seen in the attached screenshot. When there are no tenant verified domains, the applications publishers domain will be set to null and as per the table and it will show up as unverified when you get to the consent screen.
Please let me know if you have any questions. If this answer helped you please mark it as "Verified" so other users may reference it.
Thank you,
James