A team sees cloud-agnostic Sunbird architecture guidance but the installer page explicitly says its current automated support is Azure-only. What is the right OCI planning decision?

1. Run the Azure-only automation unchanged and assume it creates OCI resources
2. Rename Azure resource variables without checking provider-specific behavior
3. Conclude that Sunbird's APIs cannot be used on OCI under any circumstances
4. Validate and implement OCI-specific provisioning and integration rather than assume turnkey installer support