To add on to what @joshua said, you control the upgrade timing and therefore any resulting outages.
We don't share individual customer uptimes, since that is tied to their usage and the level of resources they have chosen for their individual deployment.
Thanks for taking the time to reply. In the scenario outlined I perhaps didn't mention that the users I was expecting the webhook to fire for already existed in FusionAuth prior to Azure AD sign-in. Should I expect the event to trigger in that instance?
@dhait Hmmm. This issue is due to the OAuth2 specification. If we provided a REST endpoint, it wouldn't be OAuth/OIDC.
If you want to fully customize the look and feel of the login and registration experience, but not use the FusionAuth hosted login pages, the recommended solution is to code directly against our REST APIs:
@markdoner27 This is a far-reaching question. Please feel free to post your question specifically as it relates to FusionAuth and we may be able to provide additional feedback.
@richb201 Heya, you need to start or install FusionAuth. It's a program like MS Word or your web browser. If you haven't used it in a while, it might be stopped.