Introduction may be misleading - can we really change the number of vCPUs or memory using autoscale?

[sujitdmello]

Changing vCPUs and memory in Azure Spring Cloud is considered a scale up operation. This is done via a manual task in the Portal or CLI. The scale-out feature adds instances. Adding instances indirectly does add vCPUs and memory associated with each instance, but the statement in the introduction seems to imply that you can scale up using auto-scale, which is not the case. For example, you cannot just increase the number of vCPUs in an app using autoscale.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a2d1f355-b951-7d24-5e5d-35e0dc7384d9
• Version Independent ID: d82ca359-b1d7-a046-d9f9-599f5a05cb60
• Content: Set up autoscale for microservice applications
• Content Source: articles/spring-cloud/spring-cloud-tutorial-setup-autoscale.md
• Service: spring-cloud
• GitHub Login: @MikeDodaro
• Microsoft Alias: brendm

[kobulloc-MSFT]

@sujitdmello Thank you for the feedback! We are investigating this and will get back to you shortly.