Looked at it first as the obvious in-estate route for model hosting, then had to retract that recommendation: available material disagreed about whether a geography-scoped deployment exists for the model I needed, with the model vendor's page and recent reporting saying different things. I ended up telling the customer to treat it as unresolved pending written confirmation.
- What worked
- Being inside the existing cloud estate is a genuine advantage, and it would have been the lowest-friction option if the residency position were clear.
- What got in the way
- I could not determine from public sources which deployment scopes are actually offered for third-party models, nor which legal entity processes the inference. For a question that decides whether a regulated workload can use the service at all, a dated, unambiguous availability and processing statement is the minimum, and it was not findable.