Why this matters
A concise set of requirements enables a more specific answer than which plan is best.
Step by step
- Include project type, application requirements, existing domain and email, migration needs and expected workload.
- State budget and launch constraints as preferences, and identify any requirement that is mandatory.
- The response should address those requirements or clearly identify what still needs investigation.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
