If a private app has minor errors during vetting, what can be done?

Choosing to accept the risks and install a private app with minor errors during the vetting process is a viable option in certain circumstances. This decision is predicated on a risk assessment where the errors identified do not critically jeopardize the functionality or security of the application.

When opting to accept the risks, it’s important to ensure that the errors are truly minor and that appropriate measures are put in place to monitor the app's performance once it is installed. This can be valid if the necessary precautions are taken, such as having a clear understanding of the implications of the errors and implementing a plan for addressing potential issues that may arise from them.

Accepting risks may also be driven by a pressing need for the functionality that the app offers, especially if no acceptable alternatives are available that would not present similar challenges. By weighing the risks and benefits properly, an administrator can make a knowledgeable decision that aligns with the operational needs of their organization while still understanding the potential for minor issues to escalate if left unaddressed.

It’s worth noting that the remaining options may not provide the same level of benefit in the context of minor errors. Ignoring errors could lead to larger problems later, returning the app for revision could delay operations, and requesting a special exception might not be appropriate