LangSmith BYOC expands cloud choice

LangChain’s [November 3 announcement](https://www.langchain.com/blog/langsmith‑byoc‑aws‑gc‑azure) expands LangSmith BYOC to Azure and Google Cloud in beta; AWS remains generally available. LangChain operates the control plane and manages the data plane in the customer’s cloud. Sales provisions access. The launch separately limits trace migration to AWS. A copied workspace is not proof its history is present.

Imagine an imported Fleet agent appears in the destination workspace. Before directing work there, separate two checks: restore required secret values and confirm its selected model. The [migration guide](https://docs.langchain.com/langsmith/byoc‑migration) says secrets become empty placeholders and unavailable source models can be substituted, with substitutions logged. A successful object copy therefore cannot establish working credentials or unchanged model identity. If answers differ after cutover, verify the model choice before attributing the difference to the move. Each user must also reconnect OAuth. This is a documented acceptance scenario, not a migration or output comparison we ran. Conceptual diagram: OpenTools Team; selected checks from LangChain’s migration guide, not a performed migration.

The [responsibility model](https://docs.langchain.com/langsmith/byoc‑shared‑responsibility) leaves application validation with the customer while LangChain operates BYOC‑managed services. Give the credential/reconnection owner and application owner separate sign‑offs: one restores access, the other confirms the intended model and application behavior. The undated guides describe current requirements; their individual details are not all newly launched on November 3.