Training: Instruction to develop new skills.
No, there's nothing wrong with doing it that way. The two-app advice in that known issue is about how the enterprise app was created, not about mixing SSO and provisioning.
The docs say that when you start from an app registration, the enterprise app (service principal) it creates isn't enabled for automatic provisioning. That's why they suggest a second non-gallery app for SCIM. You started from Enterprise applications > New application > Create your own application instead, which makes a non-gallery app that does support provisioning. Configuring OIDC on that same app afterwards doesn't take that away, so one app is a valid setup for a single-tenant, non-gallery app.
A few things to keep in mind with one app:
- Assignment drives both. Users and groups you assign get SSO access and are also in provisioning scope (if scope is "assigned users and groups"). If you ever need different populations for sign-in and provisioning, you'd need two apps.
- Test provisioning on demand with one user before you turn on the cycle, so you can confirm the SCIM endpoint and attribute mappings.
Is the app only for your own tenant, or might other organizations sign in to it later?
If this confirms your setup, please consider accepting it as the answer. If provisioning or sign-in behaves oddly later, let me know and I'll be happy to keep helping.
Reference: