Onboarding Follow-up

If you used the fully automated onboarding process, the only user who has permissions to do anything in the OracleDB for Azure portal is the user who onboarded to the service.

During onboarding, you may have granted this user the "Owner" role in one or more subscriptions in Azure. At this point, that role assignment is no longer needed. Instead, change the user's role assignment to "Contributor" in each affected Azure subscription. The Contributor role is the only subscription role users need to use OracleDB for Azure.

Next, configure one or more additional users (for example, database and application developers who will being using OracleDB for Azure databases on an ongoing basis). See Adding OracleDB for Azure Users in Azure After Completing Your Sign Up for more information.

If you used the guided onboarding process, the user who completed onboarding can login to the OracleDB for Azure portal, but not really do anything there. Before users can do anything productive using OracleDB for Azure, you must first complete configuration steps for each user or user group.

First, administrators must assign users the appropriate roles in the Azure ODS Application based on the tasks the uses are expect to perform in OracleDB for Azure. Administrators assign these roles directly to users or existing Azure groups or add users to the groups OracleDB for Azure added to the Azure tenant's Azure Active Directory. Review the role descriptions and instructions for assigning them to users in the following topics: To assign OracleDB for Azure enterprise application ARM roles to users.

Next, Azure users creating database resources in OracleDB for Azure must have the "Contributor" role assigned to them in every Azure subscription in which they expect to provision database resources. For instructions on how to assign this role to user, refer to To assign OracleDB for Azure ARM roles to users within an Azure subscription.