---
id: post/demiliani-com/13676
type: post
title: "Business Central Cloud Migration: be careful on reusing the same self-hosted runtime."
summary: Cloud migration in Dynamics 365 Business Central uses integration runtime to replicate data from on-premises SQL Server or Azure SQL to the cloud. Do not reuse the same self-hosted integration runtime across different migrations, as it becomes disabled after migration completion or 10 days of inactivity, causing setup errors.
tier: community
language: en
tags:
  - cloud migration
  - integration runtime
  - on-premises
  - data replication
  - azure data factory
system: integration
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:55:26.425Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: dbee3d6358a33c91cda2a784e9a52d2d34816f636cb7b7e698477b31458dc71c
evidence:
  - kind: blog
    url: https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/
    title: "Business Central Cloud Migration: be careful on reusing the same self-hosted runtime."
    date: "2026-04-24"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/
    title: "Business Central Cloud Migration: be careful on reusing the same self-hosted runtime."
    date: "2026-04-24"
    commit: null
    t: null
    quote: When one environment completes the cloud migration process, it disables the cloud side of the integration runtime, making it unusable for the other environments.
  - kind: blog
    url: https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/
    title: "Business Central Cloud Migration: be careful on reusing the same self-hosted runtime."
    date: "2026-04-24"
    commit: null
    t: null
    quote: To prevent this, you should not share integration runtimes between environments.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "13676"
source_id: demiliani-com
source_name: Stefano Demiliani
url: https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/
published_at: "2026-04-24T09:15:14.000Z"
author: Stefano Demiliani
full_text: false
words: 342
quotes:
  - text: When one environment completes the cloud migration process, it disables the cloud side of the integration runtime, making it unusable for the other environments.
    why_it_matters: Explains the core issue that causes failures when sharing integration runtimes between migrations
  - text: To prevent this, you should not share integration runtimes between environments.
    why_it_matters: Provides the critical best practice recommendation to avoid migration failures
code_objects_mentioned: []
systems:
  - integration
  - administration
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/embed/
  image: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/media/cloud-migration-overview.svg
  image_alt: Shows components of cloud migration
  image_w: null
  image_h: null
  site_name: Stefano Demiliani
  favicon: https://demiliani.com/wp-content/uploads/2022/09/sd_wordpress_logo.png?w=32
  probed_at: "2026-10-07T11:50:42.908Z"
---

# Business Central Cloud Migration: be careful on reusing the same self-hosted runtime.

[Read the post](https://demiliani.com/2026/04/24/business-central-cloud-migration-be-careful-on-reusing-the-same-self-hosted-runtime/) · Stefano Demiliani (Stefano Demiliani, MVP) · 2026-04-24 · 342 words · tier community · reviewed (checked by Opus)

> Cloud migration in Dynamics 365 Business Central uses integration runtime to replicate data from on-premises SQL Server or Azure SQL to the cloud. Do not reuse the same self-hosted integration runtime across different migrations, as it becomes disabled after migration completion or 10 days of inactivity, causing setup errors.

## Key points

- Cloud migration requires self-hosted integration runtime for SQL Server databases and Azure Integration Runtime for Azure SQL databases
- The self-hosted runtime must be installed locally, registered in Azure Data Factory, and securely copies data to cloud pipelines
- Reusing the same integration runtime across different migrations causes the error 'tenant has not been set up with a valid integration environment'
- Integration runtime becomes disabled after migration completion or when inactive for more than 10 days
- Each cloud migration should use its own dedicated integration runtime to avoid conflicts

## Quotes

- "When one environment completes the cloud migration process, it disables the cloud side of the integration runtime, making it unusable for the other environments." (Explains the core issue that causes failures when sharing integration runtimes between migrations)
- "To prevent this, you should not share integration runtimes between environments." (Provides the critical best practice recommendation to avoid migration failures)

## Context

- Features: Cloud Migration, Self-Hosted Integration Runtime, Azure Integration Runtime, Data Replication Pipeline

Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.