Manufacturing · Enterprise · $320K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
Director of Data Platform
Enterprise Security Architect
Manufacturing · Enterprise · $320K · owned by Yusuf Abdel-Rahman
Steve has not written one for this account. Everything it would read is below.
Every record Steve is allowed to cite
Director of Data Platform
Enterprise Security Architect
Cloud Platform Lead, EMEA
VP Infrastructure
Next step: Azure reference architecture review on 2026-07-23
Lena asked for the connector inventory in the EU region ahead of the EMEA plant cutover. Confirmed 14 of 19 connectors are generally available in Frankfurt. The SAP and Snowflake CDC connectors remain us-east only, with no committed EU date. Answer provided in writing.
Atlas requires private ingest in both target Azure regions and cannot route analytics traffic over public endpoints under their new network standard. AWS PrivateLink is GA today. Azure Private Link is on the roadmap without a committed date. Ticket held open pending the architecture review.
Investigated a sharp p99 regression on the plant telemetry workspace. Traced to a cross-cloud round trip after Atlas relocated the EMEA plant telemetry source into Azure North Europe as a pre-migration pilot, while the workspace stayed in us-east. Advised colocating the read path. p99 returned to 610ms once Atlas moved the read replica. No platform-side fault found.
Anders requested written confirmation that EU plant telemetry never leaves the EU region, covering primary storage, backups, and any support engineer access path. Draft documentation prepared, held for legal review on the Vantage side before it can be sent.
Bill said the platform has been stable and that reliability is not what he is weighing. His question is whether the architecture follows Atlas onto Azure inside the migration window his team has already committed to the board. Karen mentioned her platform group is standing up an internal lakehouse on Azure for raw plant telemetry. Nobody put a decision date on the renewal beyond the existing August close.
Anders is working to a new group policy that keeps EU plant telemetry inside the EU, including backups and any vendor support access. He asked for the key custody model and whether customer managed keys are supported in the EU region. He also pulled three open items from last year's pen test summary and asked for them to be restated against the current architecture. He took no position on the renewal itself.
Atlas is moving its analytics estate off AWS and onto Azure across the next three quarters, starting with the EMEA plants in Q4. Lena walked the target topology: Azure North Europe for EU workloads, Azure East US for everything else, private networking mandatory in both. The current us-east deployment sits outside that plan and Karen asked directly what a supported Azure path looks like and what it costs her team to get there.
Cloud Platform Lead, EMEA
VP Infrastructure
Next step: Azure reference architecture review on 2026-07-23
Lena asked for the connector inventory in the EU region ahead of the EMEA plant cutover. Confirmed 14 of 19 connectors are generally available in Frankfurt. The SAP and Snowflake CDC connectors remain us-east only, with no committed EU date. Answer provided in writing.
Atlas requires private ingest in both target Azure regions and cannot route analytics traffic over public endpoints under their new network standard. AWS PrivateLink is GA today. Azure Private Link is on the roadmap without a committed date. Ticket held open pending the architecture review.
Investigated a sharp p99 regression on the plant telemetry workspace. Traced to a cross-cloud round trip after Atlas relocated the EMEA plant telemetry source into Azure North Europe as a pre-migration pilot, while the workspace stayed in us-east. Advised colocating the read path. p99 returned to 610ms once Atlas moved the read replica. No platform-side fault found.
Anders requested written confirmation that EU plant telemetry never leaves the EU region, covering primary storage, backups, and any support engineer access path. Draft documentation prepared, held for legal review on the Vantage side before it can be sent.
Bill said the platform has been stable and that reliability is not what he is weighing. His question is whether the architecture follows Atlas onto Azure inside the migration window his team has already committed to the board. Karen mentioned her platform group is standing up an internal lakehouse on Azure for raw plant telemetry. Nobody put a decision date on the renewal beyond the existing August close.
Anders is working to a new group policy that keeps EU plant telemetry inside the EU, including backups and any vendor support access. He asked for the key custody model and whether customer managed keys are supported in the EU region. He also pulled three open items from last year's pen test summary and asked for them to be restated against the current architecture. He took no position on the renewal itself.
Atlas is moving its analytics estate off AWS and onto Azure across the next three quarters, starting with the EMEA plants in Q4. Lena walked the target topology: Azure North Europe for EU workloads, Azure East US for everything else, private networking mandatory in both. The current us-east deployment sits outside that plan and Karen asked directly what a supported Azure path looks like and what it costs her team to get there.