The answer to your question somewhat depends on your configuration and how you are wanting things to work. For example, although a user may not be created in Okta, it could certainly be imported into Okta from another app (e.g. Active directory, HR system, etc.) and thus they could also be provisioned to a downstream app (Salesforce, ServiceNow, etc.). The processing that is done on those users while they are in Okta could certainly affect the attributes that are pushed to downstream apps or they could affect the status of the account once it is imported into Okta. Sign-on settings could affect the users ability to login to Okta and/or integrated applications as well, to include MFA behavior and network zone.

Also, if you are dealing with Active Directory users, this would also apply for matters such as account status or password policy/usage. Would you be able to provide a bit more specificity in relation to your issue/question?

I hope that helps! Thanks!