Microsoft for Startups Founders Hub: Clarification needed on workload definitions and the $1 spend threshold for Milestone 3 progression

For Milestone 3, the documented requirement is:

1. Use 5 or more Azure workloads
2. Maintain them over a sustained period of about 60 days
3. The 60-day clock starts only once the required number of workloads is present
4. Each workload must have at least $1 in spend and remain above that threshold for all 60 days

On the two specific points:

1. What counts as a workload The documented definition is that a workload is an Azure service actively used in the solution. The examples given are unique service types such as:
   • Virtual Machines
   • AI and machine learning services
   • Databases
   • Application hosting services
   Based on that definition, workload counting is tied to unique Azure services, not to the overall application as a single unit. The documentation does not provide a more detailed telemetry algorithm for how composite resources are grouped internally. It also does not explicitly state whether a VM plus its managed disk is treated as one workload or two for milestone counting. The supported conclusion is only this: if the services are treated as distinct Azure services, each unique service can count toward the workload total.
2. Meaning of the $1 threshold The documentation does not describe this as a daily $1 minimum run rate. What it does say is:
   • the 60-day clock starts when the required number of workloads exists, each with at least $1 in spend
   • every workload must stay above $1 in spend for all 60 days
   • if any workload drops below the threshold, the startup falls below the required number and the count only completes after 60 continuous days at or above the target
   So the supported interpretation is that this is a continuous eligibility condition across the 60-day period, not a one-time aggregate spend check at the end. The documentation does not define the exact billing math at daily granularity, so it does not confirm a per-day calculation model.

For architecture planning, the safest documented approach is:

1. Ensure at least 5 distinct Azure services are actively in use.
2. Ensure each of those services reaches more than $1 in spend.
3. Keep all 5 services continuously active for the full 60-day window so none falls below the threshold.
4. Do not rely on one-time spikes, because progress is evaluated on recent activity and sustained usage patterns, not one-time spikes.

If exact interpretation is needed for a VM plus managed disk scenario or for how the threshold is computed in telemetry, that falls into a program-rules clarification request. Microsoft for Startups Program Support is in scope for Azure credit usage questions and program-related issues.

• Getting started with Microsoft for Startups
• Getting started with Microsoft for Startups
• Microsoft for Startups Program Support