Hands-on Exam Practice

Azure is usually easier to provision for individual practice than Microsoft 365 because you can create your own subscription and resources. However, many Azure services use consumption-based billing. Before deploying anything, identify the pricing model, estimate the cost, configure alerts, and decide how you will remove the resources when the exercise is complete.

The Azure free account includes limited credits, free monthly service amounts, and spending protection under its current terms. Pay-as-you-go accounts can consume services beyond free amounts and do not have the same spending protection. Check the current offer and eligibility rules before signing up or upgrading.

Product Pricing

Official Azure Pricing

Review every billable component, including compute time, storage, backups, public IP addresses, network egress, supporting services, and Marketplace products. The price shown during resource creation may not represent the entire solution.

Azure Pricing Calculator

Use the calculator to estimate a complete lab configuration. Match the region, tier, runtime, storage, and expected usage to what you plan to deploy.

Cost Controls

Budgets

Budgets can alert you about actual or forecast spending, but a budget does not cap spending or stop resources. Cost data and alerts can also be delayed. Configure low thresholds, monitor Cost Analysis directly, and never rely on an alert as your only protection.

Budgets can trigger action groups or other automation when a threshold is reached, but that response must be configured separately. Test any automated shutdown or deletion process carefully because dependencies, delayed cost data, and destructive actions can produce unexpected results.

Anomaly Cost Alerts

Anomaly alerts identify unusual changes relative to previous usage. A new lab deployment can legitimately trigger one, so investigate the underlying resources instead of assuming every alert is an error.

Cleanup Checklist

1. Delete the lab resource group when the exercise is complete.
2. Check All resources for anything created outside that group, including hidden or automatically created resources.
3. Review Marketplace or SaaS subscriptions and support plans separately because deleting an Azure resource group may not cancel them.
4. Review Cost Analysis again after cleanup because usage data can arrive later.
5. Cancel the Azure subscription if you no longer need it and understand the effect on retained data and the final bill.

Microsoft 365 practice usually requires access to a separate tenant and suitable licenses. Availability depends on your organization, region, role, and eligibility for current trials or developer programs.

Eligible members of Microsoft partner programs can check Microsoft Demo Experiences for demo environments. Qualified Microsoft 365 Developer Program members, including eligible Visual Studio Professional or Enterprise subscribers, can apply for a renewable Microsoft 365 E5 developer subscription.

Product trials change frequently and may require an existing tenant, administrator permissions, a payment method, or recurring billing. Confirm the current duration, included products, conversion terms, and cancellation process on the offer page before starting.

If an eligible offer requires a tenant and you do not already have one, Microsoft provides a work or school account signup flow. Creating the tenant does not itself provide the product licenses required by a lab, so confirm the license and administrator requirements before proceeding.

Paid Microsoft 365 enterprise subscriptions can cost substantially more than a short Azure lab, especially when annual or multiyear commitments apply. Compare the required licenses, number of users, billing term, trial conversion behavior, and cancellation rights rather than comparing only the advertised monthly amount.

Cleanup Checklist

1. Record the trial end date, billing term, and recurring-billing status when you sign up.
2. Remove or export test data that you need to retain.
3. Cancel trials and subscriptions through the correct billing account before they convert or renew.
4. Confirm whether removing licenses actually ends the subscription; license assignment and billing are separate operations.
5. Review any annual or multiyear commitment before purchasing because reducing users or removing licenses may not remove the remaining payment obligation.
6. Delete test users, applications, connectors, and credentials when the environment is no longer needed.

The Power Apps Developer Plan provides an environment for developing and testing Power Apps, Power Automate cloud flows, and Dataverse solutions. It requires an eligible work or school account, is not licensed for production use, has capacity limits, and can be disabled after inactivity.

The Power Apps Developer Plan does not include installable Dynamics 365 applications. For Dynamics 365 practice, use an app-specific official trial or an environment supplied by your employer, training provider, or eligible Microsoft program. Trial availability and duration vary by application and region.

Use the same lifecycle discipline as other environments: keep synthetic data only, document dependencies, export anything you need, and delete or reset development environments when they are no longer required.