Favor one-off manual changes over repeatable configuration. It does not resolve unclear data lineage in the identity program.

Use deprecated interfaces without checking project guidance. It skips the need to validate dependency readiness before cutover before retiring the legacy process.

Choose the maintainable, auditable approach that matches the project architecture and operational model. For this case, also validate dependency readiness before cutover and address unclear data lineage before closure.

Ignore security boundaries because the environment is internal. It weakens measurable business value during a security architecture review and creates operational fragility.