Following up and closing this thread - this issue was sorted via another discussion.
For folks in the future with this issue, note the following support article: