Azure AI Search Over-provisioned
The service bills per replica and partition provisioned, independent of query volume, so units beyond what the index and traffic need are billed idle.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce replicas or partitions on the AI Search service. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- AI Search on Azure
- The fix, by hand
- Azure Portal → your Search service → Settings → Scale.
- Review query volume (Monitoring → Metrics → Search Queries Per Second) and latency before changing capacity.
- Reduce replicas and/or partitions (floor is 1 replica × 1 partition).
- Note: scaling is not instantaneous and 2+ replicas are required for the read SLA (3+ for read-write). Keep enough for your availability target.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1396- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.