Skip to main content
Question

Real-world experience with Self-Hosted BI / Analysis Models infrastructure (Scenario 3 Azure vs on-prem)?

  • June 2, 2026
  • 1 reply
  • 18 views

Forum|alt.badge.img+1
  • Do Gooder (Customer)

Hi all,

We're on IFS Cloud (managed SaaS, hosted by IFS, 25R2) and we're evaluating enabling Analysis Models (Tabular) with self-hosted BI infrastructure. We've been working through the technical docs but, before committing, we'd love to hear from people who've actually been through it.

 

Docs we've been looking at:

A few questions for anyone who has deployed this in production — either managed service (IFS-hosted + Azure BI) or on-premise:

  1. Did you stand up the full stack (Azure SQL DW + Data Factory + SSIS-IR + Azure Analysis Services), or did you manage to simplify any part of it? Anything you'd skip in hindsight?
  2. Upgrade maintenance — how much effort is it to keep the models/packages working across IFS Cloud releases? Are the models/packages of IFS working smoothly or did you have to maintain them somehow ?
  3. Did anyone consider (or actually use) their own ETL against IFS data instead of the packaged SSIS flow, and how did that go support-wise?

Any lessons learned, gotchas, or rough timelines would be hugely appreciated. Happy to share back what we end up doing.

Thanks!

1 reply

Forum|alt.badge.img+4
  • Sidekick (Customer)
  • June 3, 2026

We started with scenario 3 since it was the only solution recommended by IFS Consulting at that point in time.

Since we’re not using the pre-made BI reports and how all our other DW data in Snowflake we have since moved away to a more streamlined solution of using DF → Snowflake + DBT → relevant reporting/analyical layers.

We are using the solution for defining data sources within IFS, predominatly when we need incremental load functionality, and directly access view where relevant. After a couple of years of operational experience I would say it works fine. IFS configuration is a bit cumbersome, but we have had very few issues after we made this switch.