I'm writing a solution that will move an azure database out of an elastic pool, run a long and DTU intensive operation, and then move the database back into the pool. I'm trying to use azure powershell to automate the scaling part (using this as a guide). However, I noticed that when the powershell command completes, the azure portal still shows that the database has an "1 ongoing operation".
Is there some way to tell when the operation is really complete? Or perhaps is waiting for the powershell script to complete good enough? I did notice the pool membership was already updated in the portal.