Deploy PaaS Service via Release Management 2013

Hi. Today we speak about deploy to azure PaaS Service.

Before release Management, a lot of DevOps deploy package to azure via powershell script.

To automatize this process build engineer should be customize build template and execute this powershell script in build server in tfs.

But when was released "Release Management", the build engineers can move deploy load to Release manager server. And this is logical, because build servers should build, but not deploy.

But in current version of Release Management 2013  doesn't exist good mechanize.
In Release Management exist Release : VNext and Agent Based.
And this is a problem. Because this Release works with IaaS.

How about PaaS?

In this case we should use Agent Based + our PowerShell Script which deploy package to PaaS.
Why we can't use VNext? Because if you create a queue in VNext, you will be have a problem. Because VNext can't work  with queue and throw exception if they have more that on queue.

Please note!

Please note, that TFS, Release Management, Agent Base Server should be in one domain controller.

User, which connect agent based server with release management should have admin permission in RM.