I got the answer from Support as :
When customer initially deployed service it got deployed under the cluster which does not support high memory VM's. Since customer is having deployment under the hosted service it cannot be pinned/migrated to a cluster which supports A6 or higher VM size. This is a by design behaviour as of now. Unfortunately, the only way customer can deploy a A6 VM is to delete and recreate deployment with A6 size under the given hosted service. When customer tries to create it, then he/she will be allocated a cluster which supports A6 or higher VM size.