error during adding automatic firewall rule about vsts-release-aas HOT 4 CLOSED

I got the deployment to pass. We where using Developer pricing tier on AZ AS, so I changed it to basic or rather to standard since we're using perspectives...
Seems like the firewall rule stuff only applies to pricing tier Basic or higher. We are using Developer for development, but in this pricing tier the firewall feature isn't available (I guess?).
Could the extension take this into account so that it's possible to disable the firewall rule add/delete with an option?

from vsts-release-aas.

If your Analysis Service admin has MFA enabled, the pipeline cannot run unattended as the MFA expects a user interaction.
It is better to add a service principal as Analysis Service admin and use those app id/secret to login and deploy the new model.

from vsts-release-aas.

@liprec Thanks for a quick reply.
We've fixed the MFA problem. They had a special policy that require MFA for login made from other countries than their countries where they are engaged, so that is sorted out.
I will re-test deployment against an azure analysis service in Dev tier, and will add an issue if there is a problem with that or have you tested to deploy to a D1 pricing tier?
we can close this issue, after your feedback on the D1 tier deployment.

from vsts-release-aas.

It works for D1 tiers as this is the tier I am using to test my tasks due to costs 😉.
And indeed re-open this issue if you are still having issues.

from vsts-release-aas.