Is Microsoft halal in 2026? AAOIFI screen + live API verdict
Is Microsoft halal? The AAOIFI screen, the financial ratios, and the live verdict from the Akinda API for MSFT.
Current verdict: Doubtful
Company snapshot
Microsoft Corporation trades under the ticker MSFT and operates in the Software / cloud computing sector. The Akinda API runs every ticker through the same three-phase screen — business activity, financial ratios, and a final verdict — so the verdict above traces back to the numbers below.
Phase 1: Business activity screen
First we check what Microsoft Corporation actually does. The AAOIFI rule for mixed-business companies says non-compliant revenue must stay below 5% of total revenue, with no exposure to outright-prohibited sectors (alcohol, conventional banking and insurance, gambling, tobacco, pork, weapons, adult content).
- Productivity & Business Processes — Microsoft 365, Dynamics, LinkedIn. Permissible.
- Intelligent Cloud — Azure, server products. Permissible.
- More Personal Computing — Windows, Xbox, search advertising, devices. Gaming content and search advertising contain the non-compliant exposure.
Non-compliant revenue percentage on /full-report/MSFT: 5.81%. Field name on the wire: non_compliant_revenue_perc.
Phase 2: Financial ratio screen
After the business activity screen clears, the strict AAOIFI grid we apply requires two financial ratios — debt and liquidity / interest-bearing cash position — each below 30% of the company's average 12-quarter market capitalization. Numbers below are the most recent values returned by /full-report/MSFT.
Debt ratio (< 30%)
1.39%
debt_ratio_perc
Liquidity (< 30%)
3.05%
liquidity_ratio_perc
Notes for investors
The non-compliant revenue percentage sitting at 5.81% places Microsoft above the 5% AAOIFI cut-off, which is what flips the verdict to Doubtful instead of Halal. Investors using stricter index-provider methodologies (with the 36-month market-cap denominator) may see different results.
Verify it yourself via the Akinda API
Fire a live /full-report/<ticker> call from the playground using your own API key — see the compliance ratios, AAOIFI screen verdict, and source-breakdown fields the methodology produces.
Related reading