Fabric Apps developer for Riyadh
Fabric Apps Developer in Riyadh
Internal tools on Microsoft Fabric for Riyadh teams, built with a clear view of what preview means.
Fabric Apps lets us build internal applications directly on the data your reports already use. We use it for approvals, data entry, forecast overrides and reference-data editors. It is in public preview, so we scope it for internal use.
- Riyadhالرياض
- Dubai AI Campus, DIFC
- 1 hour time difference
- About 2 hours by air
We serve Riyadh from our Dubai office in DIFC, one hour ahead of Riyadh and on the same working week from Monday to Thursday.
Riyadh at a glance
Riyadh, Saudi Arabia
24.71° N, 46.68° E
- where our Fabric Apps already run
- UAE North
- clients across the GCC and Europe
- 25
- of them government entities
- 12
- time difference with Riyadh
- 1 hour
When a dashboard is not enough, build a Fabric App
Fabric Apps let us build the internal tools that sit beside your reports: approvals, forecast overrides, data entry and reference-data editors. They run on the same Fabric data and the same security as your Power BI reports, so there is no separate stack to host, secure and pay for. We already have Fabric Apps running in UAE North.
Riyadh
No Fabric region yet
UAE North
Dubai
- Fabric capacity region
- Riyadh, no Fabric region yet
Fabric has no region inside the Kingdom yet. Microsoft plans a Saudi Arabia East Azure region from November 2026, but Fabric support there is not confirmed, so for Riyadh teams we settle at the start which data can sit in a UAE or European capacity and which stays on your own servers.
- 01
One item, not four services
A database, an API, Entra sign-in and hosting come as one Fabric item, with no embed tokens.
- 02
Your security carries over
Every query runs as the signed-in user, so the row-level security in your semantic model applies inside the app.
- 03
Days, not months
From a Power BI semantic model to a working app in days, instead of weeks of custom integration.
- 04
Straight about the limits
Fabric Apps suit internal tools. Citizen-facing portals and always-on systems still need a custom build, and we say so up front.
Local context
Where Fabric Apps fits for Riyadh organisations
01Fabric Apps has been in public preview since June 2026 and is not yet available in every Fabric region. We already run it in UAE North, which is the nearest Fabric region to Riyadh. For a Riyadh team that means an app built on data held in a UAE capacity, so the question of which data may leave the Kingdom has to be answered before any app is designed.
02That limits the best uses to internal tools on data you are already allowed to process in the UAE: budget submissions, programme status updates, supplier approvals and corrections to reference tables. Personal data covered by the Personal Data Protection Law, or data your classification marks as restricted, belongs in a system that stays inside the Kingdom.
03We do not recommend Fabric Apps for portals used by citizens or customers. Preview terms can change, and a public service needs support commitments that a preview does not give. For those cases a conventional application is the safer choice, and we say so at the start rather than after the build. The same advice applies if the data in question is still waiting on a Saudi region to be confirmed.
Sample report
What your leadership sees, in Arabic and English
A sample report with illustrative figures. Switch to عربي to see the right-to-left version with Hijri dates.
مطور تطبيقات Fabric في الرياض
نبني تطبيقات داخلية على بيانات Fabric، مثل الموافقات وإدخال البيانات وتعديل التوقعات. ولأن Fabric Apps في مرحلة المعاينة العامة، نحصر استخدامها في الأدوات الداخلية.
Key indicators
Regulation
Built around Saudi Arabia's data rules
Personal Data Protection Law (PDPL)
Enforced since September 2024. We design access, retention and masking around it.
NDMO data management standards
Followed by government bodies and their partners. Our documentation maps to them.
Data stays in your tenant
Work happens in your Microsoft environment, where your data stays.
A general summary, not legal advice.
Focus areas
Where Riyadh teams start
- 01
Approval workflows on report data
Requests reviewed and signed off in the same place the numbers are read.
- 02
Budget and forecast input
Planned figures entered and overridden by owners, with a record of who changed what.
- 03
Reference-data editors
Controlled screens for maintaining the lists and mappings your reports depend on.
- 04
Programme status updates
Initiative owners submit progress that flows straight into leadership reports.
Clients
Trusted by programmes and enterprises in the Kingdom
In the Kingdom

National Technology Development Program
Government programme, Riyadh

Royal Commission for Al-Ula
Government, Riyadh and AlUla

Aramco Digital
Energy and digital, Eastern Province
Across the GCC and Europe
Beyond The Analytics successfully migrated our organization wide Tableau reporting infrastructure to Power BI with a strong focus on continuity, data integrity, and user confidence throughout the process. The team was professional, structured, and technically strong, making the transition seamless and leaving us with a scalable analytics environment.
Arun RodriguesModern Applications Manager, Al-BaharEngagement
What the work covers
What we do
- Approval and sign-off workflows on Fabric data
- Data entry forms that write back to the lakehouse
- Forecast and budget override screens
- Reference-data editors with change history
- Access control through Microsoft Entra ID
- Advice on where a Fabric App stops and a custom app starts
What you receive
- A working internal app on your Fabric workspace
- A write-back design that protects your source tables
- A usage and capacity estimate for the app
- A written note on preview limits and the exit options
Stack
- Microsoft Fabric
- Fabric Apps
- OneLake
- Power BI semantic models
- Microsoft Entra ID
- Fabric Lakehouse
Process
Four steps from first audit to handover
- 1
Choose
We confirm the use case suits an internal Fabric App. If it needs public users or heavy custom screens, we say so.
- 2
Model
We prepare the semantic model and the tables the app reads and writes, including who may change what.
- 3
Build
The app is built and shown to its users within days, then adjusted in short rounds.
- 4
Release
We set permissions, estimate capacity use and document the preview limits so you can plan around them.
From the blog
Further reading
For leaders weighing the cost, risk and payoff of their reporting.
- Microsoft FabricRead the article
Microsoft Fabric Apps and Rayfin: What the New App Layer Does
Learn which of the four Fabric app capabilities fits your scenario: new Fabric Apps preview, Rayfin SDK, translytical task flows, or Power Apps on OneLake.
- Microsoft FabricRead the article
Fabric Apps vs a Custom Web App: What Each Can Actually Run
Fabric Apps vs a custom web app: what each can host, where Fabric Apps stops, and the preview, region and licensing limits to check first.
- Microsoft FabricRead the article
Fabric Apps Pricing: What Pro Covers and What Uses Capacity
Fabric Apps pricing, worked out: a 40-user app needs F4, not F2, because the SQL database floor alone uses 87% of an F2. UAE North rates included.
- Microsoft FabricRead the article
Power BI or a Custom App? One Rule for Where a Feature Lives
When to use Power BI vs a custom application: one rule, ten worked examples, and why write-back going GA moves the line less than most teams assume.
Questions
Asked by teams in Riyadh
Anything not covered here, we can answer on a short call.
More locations






