Strategic consideration
Below you can learn more about key strategic factors to consider before application onboarding (either manually or through the guided onboarding process).
Step 1: Choose the applications to be onboarded
The Application onboarding process entails a collaboration between the Business and IT. Not all resources will require applications, and the scope of application onboarding can vary from business to business. However, there are some general guidelines on how to approach this process.
Step 2: Create an overview
A good starting point is to create a breakdown of applications to be onboarded that includes information on which applications are AD-controlled, need system integration, or need an API, for example:
| Application Name | AD-Controlled? | Comments |
|---|---|---|
| Report on Financial Postings | Yes | |
| Omicron | No | Needs API / integration path |
| Zeta | No | Oracle-based – System Onboarding for Oracle Needed |
Step 3: Onboard with Active Directory
Active Directory is usually one of the first systems to be onboarded. It provides a good starting point for evaluating the amount of collaborative effort that will be needed during the application onboarding process.
Step 4: Prioritize resources according to business criticality
Try to answer the following questions:
- Which resources contain business-critical access rights?
- Which resources contain highly sensitive information?
- Which resources does the business need to control for auditing and compliance purposes?
Step 5: Select applications to run test onboarding
Choose a few business-critical applications and follow the instructions of the manual onboarding process or the guided onboarding process.