Intellectual Integration

Intellectual Integration for Business

SAP on Azure · Data & AI

Features & Specializations

All competencies

Scientific Potential

>50% PhDs in IT

of our team hold PhDs in IT & AI

Doctoral-level research experience meets enterprise delivery: we design integrations and models with scientific rigor and build them to run reliably in production.

About

A system integrator with a scientist’s approach

FEONA Oy is a Finnish system integrator based in Espoo. We connect enterprise systems and data platforms — SAP, Microsoft Azure, Power BI and Snowflake — and build the analytics and AI that run on top of them.

We take on focused projects for companies that need integration, reporting or machine-learning expertise, and we can also join larger delivery teams as a subcontractor. Our approach is simple: clear hypotheses, measurable results and documentation your own team can maintain.

Competencies

SAP on Azure, from infrastructure to AI

The skills we bring to SAP projects on Microsoft Azure — for new landscapes, migrations and the systems you already run.

  • SAP on Azure infrastructure

    • Sizing on SAP-certified Azure virtual machines
    • Storage design with Azure NetApp Files, Premium SSD v2 and Ultra Disk
    • Landing zones, networking and governance with Azure Policy

  • S/4HANA migration and RISE with SAP

    • Planning and executing ECC to S/4HANA migrations
    • RISE with SAP on Azure: ExpressRoute, VNet peering, DNS, identity and security
    • Transformation management with SAP Cloud ALM

  • High availability and disaster recovery

    • SAP HANA System Replication with Pacemaker clusters (STONITH, SBD)
    • Disaster recovery across regions with Azure Site Recovery
    • Backup policies and regular restore tests

  • Automation and operations

    • Infrastructure as code: Bicep, Terraform and SAP Deployment Automation Framework
    • Azure Center for SAP solutions and Azure Monitor for SAP solutions
    • Cost optimization: right-sizing, Reserved Instances and Savings Plans

  • SAP HANA and system administration

    • SAP HANA database administration
    • SAP Basis for S/4HANA and security administration
    • SAP BTP administration and clean-core extensions

  • Data and AI

    • SAP Business Data Cloud and SAP Datasphere
    • Microsoft Fabric and Power BI on SAP data
    • Joule and Microsoft 365 Copilot, machine learning in production

How we work

  1. Discover

    We map your systems, data flows and the decisions the solution has to support.

  2. Design

    Architecture, data model and security, agreed with your IT and business owners.

  3. Integrate

    Iterative delivery with automated tests, reconciliation checks and visible progress.

  4. Hand over

    Documentation, knowledge transfer and optional continued support.

Blog

Practical notes on data platforms

  • SAP HANA on Azure

    Five checks before moving SAP HANA to Azure

    Infrastructure decisions made early decide how smooth a HANA migration will be. These are the five we review first.

    2 min read
  • SAP Finance · Power BI

    Power BI on SAP Finance data without spreadsheet detours

    Finance teams trust numbers that reconcile to the ledger. A few modeling choices make that the default instead of a monthly exercise.

    2 min read
  • Snowflake

    Where Snowflake credits really go

    For most analytics teams, compute rather than storage drives the bill. Four habits keep it predictable.

    2 min read

Careers

Join our team

We are looking for senior specialists for SAP, Azure and data projects. Read the roles and ask us anything — no CV or personal data needed at this stage.

  • Senior · SAP on Azure

    Run and evolve SAP S/4HANA and HANA landscapes on Microsoft Azure — from installations and upgrades to high availability and RISE with SAP.

    • SAP HANA
    • S/4HANA
    • Pacemaker HA
    • RISE with SAP

    Espoo, Finland · Full-time or contract

    Request info
  • Senior · Azure

    Design Azure landing zones, networking and automation for SAP workloads, and lead the technical side of S/4HANA migrations.

    • Azure
    • Terraform / Bicep
    • ExpressRoute
    • S/4HANA migration

    Espoo, Finland · Full-time or contract

    Request info
  • Senior · Data & AI

    Turn SAP data into reliable reporting and machine-learning products with SAP Business Data Cloud, Microsoft Fabric, Power BI and Snowflake.

    • SAP BDC
    • Microsoft Fabric
    • Power BI
    • Python

    Espoo, Finland · Full-time or contract

    Request info

Request more information

Choose a role and what you would like to know. We reply to the email address you send the request from.

This form asks for no personal data and stores nothing on this website — it only prepares an email in your mail app.

What would you like to know?

Contact

Discuss your project

Tell us about your systems and goals. Sending the form opens a pre-filled email in your mail app — nothing is stored on this website.

Prefer email? Write to [email protected].

SAP HANA on Azure

Five checks before moving SAP HANA to Azure

Infrastructure decisions made early decide how smooth a HANA migration will be. These are the five we review first.

1. Certified compute

Run HANA only on virtual machine types and storage configurations listed in SAP’s Certified and Supported SAP HANA Hardware Directory. Size from measured memory use with headroom for working memory and growth — not from the nominal RAM of today’s server.

2. Storage layout

/hana/data and /hana/log have different latency needs. Use the storage combinations Microsoft documents for HANA — such as Premium SSD v2, Ultra Disk or Azure NetApp Files — and verify throughput with SAP’s HANA Hardware and Cloud Measurement Tools before go-live.

3. Latency between tiers

Keep application servers close to the database: same availability zone, accelerated networking and proximity placement groups where needed. Measure round-trip times between application and database instead of assuming them.

4. High availability and disaster recovery

HANA System Replication between zones with a Pacemaker cluster covers local failures; a replica in a second region covers disasters. Agree on RPO and RTO with the business before choosing the topology.

5. Restore drills

Azure Backup for SAP HANA works through the Backint interface; native file backups are another option. Either way, schedule a full restore test — the restore time, not the backup, is what the business feels.

Planning a HANA move? Discuss your project with us.
SAP Finance · Power BI

Power BI on SAP Finance data without spreadsheet detours

Finance teams trust numbers that reconcile to the ledger. A few modeling choices make that the default instead of a monthly exercise.

Start from the Universal Journal

In SAP S/4HANA, table ACDOCA holds financial and management accounting line items in one place. Building on it avoids stitching together separate FI and CO extracts.

Extract instead of querying live

Land the data in a governed layer — a lakehouse, a warehouse such as Snowflake, or SAP Datasphere — and refresh it incrementally. Heavy reporting queries should not compete with the transactions running in your ERP.

Model a star schema

Use one fact table for journal lines and shared dimensions for company code, account, cost center, profit center and period. Keep SAP hierarchies, such as financial statement versions, as proper parent–child dimensions.

Secure by row

Row-level security on company code or cost center lets one report serve every controller — without copying files around.

Reconcile automatically

A daily check that totals by company code and period match the trial balance turns trust into a test that either passes or fails.

Want reporting your finance team signs off on? Discuss your project with us.
Snowflake

Where Snowflake credits really go

For most analytics teams, compute rather than storage drives the bill. Four habits keep it predictable.

Know the billing model

A virtual warehouse consumes credits while it runs, billed per second with a 60-second minimum each time it starts or resumes. Many short resumes of a large warehouse add up quickly.

Suspend early, size deliberately

Short auto-suspend periods suit BI and ad-hoc warehouses. Scale up when the query profile shows spilling to remote storage; otherwise a smaller warehouse running slightly longer is often cheaper.

Separate the workloads

Give ELT, BI and data science their own warehouses, and set resource monitors with credit quotas so a runaway job stops before it surprises anyone.

Mind the storage you don’t see

Time Travel and Fail-safe keep history for frequently changing tables. Transient tables or shorter retention suit staging data that can be rebuilt.

Want a second opinion on your Snowflake setup? Discuss your project with us.
Senior · SAP on Azure

Senior SAP Basis & HANA Consultant

Espoo, Finland · Full-time or contract

Run and evolve SAP S/4HANA and HANA landscapes on Microsoft Azure — from installations and upgrades to high availability and RISE with SAP.

What you’ll do

What we’re looking for

Nice to have

What we offer

Request more information
Senior · Azure

Senior Azure Cloud Architect for SAP

Espoo, Finland · Full-time or contract

Design Azure landing zones, networking and automation for SAP workloads, and lead the technical side of S/4HANA migrations.

What you’ll do

What we’re looking for

Nice to have

What we offer

Request more information
Senior · Data & AI

Senior Data & AI Engineer (SAP data)

Espoo, Finland · Full-time or contract

Turn SAP data into reliable reporting and machine-learning products with SAP Business Data Cloud, Microsoft Fabric, Power BI and Snowflake.

What you’ll do

What we’re looking for

Nice to have

What we offer

Request more information