Content mirroring and workflows are not the same as "Ready to publish" or "Rejected" or "Draft" (will work). I'll come back to you regarding the requirements.
When running in Azure WebSites the additional resources needed are SQL Azure, Azure Blob Storage (media binary storage) and ServiceBus (used for communication between site instances).
The reason why workflows is not supported in Azure is that the schema/procedures used by WF .NET 3.5 (which EPiServer implementation is based on) is not compatible with SQL Azure. You can probably modify the schema to fulfil SQL Azure requirements (http://blog.huilaaja.net/2014/03/03/deploying-episerver-alloy-database-to-sql-azure/) if workflow support is nesscary.
The reason mirroring is not supported is that it requires WCF endpoint configuration between site and service. It is probably possible (have not tried it my self) to deploy a mirroring service as a stand alone Azure Web Site instance and then configure the site to use that endpoint (pretty much like the description on how to set up EPiServer Search in Azure).
Hello, I have couple of questions about deployment to AzureI have read http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-CMS/75/Deployment/Deployment-scenarios/Deploying-to-Azure-websites/
Didn't find any requirements directly related to Azure features needed to buy? Will just website with sql server support work or there is something specific to look for in an Azure offer?Also, when I read this: "- Content mirroring and workflows are not supported."
Does it mean that basic out of the box tasks are not supported as well like "Ready to publish" or "Rejected" or "Draft"?
Any advices on Azure, what to pay attention to are valuable to me.
Ah yes, I have read http://blog.huilaaja.net/2014/03/03/deploying-episerver-alloy-database-to-sql-azure/