Availability is an intersection, not a label
Your objectiveCheck all constraints that determine whether a capability can be used.
Understand the idea.
A feature may require a service, a hardware family and a region to be available together. Product names alone do not establish that intersection. Keep eligibility constraints in the decision record so a deployment does not rely on a capability that exists somewhere else but not in the intended environment.
A worked example.
The desired hardware is available in one region, and a related managed service is available in another. Neither fact alone establishes a usable combination for the proposed deployment.
Try the reasoning.
Create columns for service, region, hardware or tier, account prerequisites and verification date. Fill the matrix from current official documentation for a future real evaluation.
Carry it into practice.
Retain the official source and date for each eligibility decision.
Read the reference: IETF · HTTP semantics ↗