Microsoft MVP | AI & Fabric Specialist for Business Transformation | Helping Enterprises Unlock ROI with Azure, Copilot & Power BI | Forbes Tech | Keynote Speaker | CEO, Onyx Data

Strategic Data & AI Leader | Microsoft MVP | Oxford AI Strategist 

I bridge the gap between technical complexity and Board-level strategy. With nearly 15 years of experience, I have delivered over £93M in revenue growth for global enterprises by transforming data estates into high-velocity strategic assets.

Global Authority & Scalable Insight: 

LinkedIn Learning Instructor: Author of "How to Build and Execute a Successful Data Strategy," an industry-standard framework used by 10,000+ global learners (4.5/5 rating). 
Industry Recognition: Microsoft Data Platform MVP, Forbes Technology Council member, and Gartner Community Ambassador. 
Academic Rigor: Currently calibrating enterprise AI risk and leadership at the University of Oxford (Saïd Business School).

The "Onyx Methodology" in Action:  I help organisations move past "AI Hype" to achieve Operational Utility. Whether leading a global practice of 60+ consultants or advising the C-suite on £200TB+ migrations, my focus is on de-risking technology investments to drive EBITDA.

Core Specialisms:  AI Strategy & Governance (Purview) | Microsoft Fabric & Databricks Architecture | Data Monetisation | High-Performance Team Scaling.

Let’s connect,  I’m focused on the intersection of AI Ethics, Enterprise Strategy, and high-stakes Data Leadership. Always open to discussing the future of our industry with fellow Partners and Architects.

Leon Gordon

Think of your Fabric Capacity like a Train. 

Licensing is the #1 confusion point I see with Microsoft Fabric.

You bought a capacity, but your team still gets "Upgrade to Pro" prompts. 

Why?

It helps to visualise it like a Commuter Rail System:

🎫 The Small Train (F2 - F32): Everyone needs an individual ticket (Pro License) to board and look out the window (view reports). It doesn't matter if you own the train; the passengers still need to pay.

🚄 The High-Speed Rail (F64+): This train is so large that the "Venue" subsidises the cost. Standard Pass holders (Free Users) can ride for free just to look out the windows. This is the "F64 Magic Number."

👮 The Conductor Rule: Regardless of the train size, you always need a special license (Pro) to actually drive the train or manage the passengers (share content/workspaces).

I created this cheat sheet to break down the 3 building blocks of Fabric licensing:

1. Capacity (The Engine): Your computing power.
2. Per-User (The Driver): The Pro/PPU seats.
3. The F64 Rule: When free users can finally see content.

Save this image. It will save you from overpaying for Pro licenses you might not need.

#MicrosoftFabric #PowerBI #DataStrategy #DataArchitecture #Azure

Microsoft MVP | Oxford AI Strategist | Interim Technical CDO / Head of AI & Data | Architecting Sovereign Governance & £93M+ ROI for Global Enterprise

I Help Change the Way Intrapreneurial Chief Revenue Officers and CIOs, Turn Their CRM From Friction to Fuel so They Can Outgrow Their Competition.

Chuck Ingram

The biggest thing holding our growth back wasn’t sales.

It was ownership.
And if you’re a Microsoft seller, you’ve seen this pattern.
The first call is great.

IT is engaged.

Everyone’s aligned on why change matters.
Then the deal drifts into:

• How many users

• Which modules

• Timeline and scope
Necessary? Yes.

Deal-accelerating? Usually not.
Here’s the hard truth I learned building CongruentX:
Deals don’t stall because of features.

They stall because no one owns the outcome.
For a long time, I thought the constraint was headcount.

We just needed more sellers.
Meanwhile, partners and clients kept telling me:

“I love working with you. Why doesn’t your team talk like 'you' do?”
What they meant was simple:

My team was running a process.

I was unconsciously framing a future.

That changed when we brought on a seller who talks to clients the same way 'I' do (probably better)

On early calls, he does something different.

He asks the client to imagine us on stage together a year from now.

What changed in the business?

What changed for the CRO?

What changed for the reps?

What changed for RevOps?
Then he pulls out a simple artifact — about 25 lines — and maps how we get there together.

Not a project plan.

A pathway to outcomes.
And he keeps coming back to it.

Helping the buying committee make decisions against results, not steps.
That’s when it clicked for me:
Headcount wasn’t the constraint.

Ownership was.
If you’re selling Dynamics, or Copilot, this matters:

• Committees don’t buy modules — they buy confidence

• Champions don’t need features — they need a story they can defend

• Execs don’t want scope — they want to know what’s different after go-live
When sellers own the outcome — not just the motion — deals move faster.

And scale looks very different.

Question for Microsoft sellers:

How are you helping your deals stay anchored to outcomes not features or hours once the process kicks in?

I Change the Way Intrapreneurial Chief Revenue Officers and CIOs, Use AI and CRM as Fuel so They Can Outgrow Their Competition.

taplio

The Battle

Leon Gordon

Chuck Ingram

Followers

Posts

Engagements

Likes

Performance ScoreLeon Gordon's LinkedIn Performance

Performance ScoreChuck Ingram's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Leon Gordon

Chuck Ingram

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Leon Gordon's LinkedIn Performance

Performance ScoreChuck Ingram's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreLeon Gordon's LinkedIn Performance