Azure IaaS was announced for General Availability earlier this week. http://blogs.msdn.com/b/windowsazure/archive/2013/04/16/the-power-of-and.aspx. FIM is supported as a workload on this infrastructure. We can see additional documentation on this here (http://support.microsoft.com/kb/2721672). The Microsoft Knowledge Base article cannot hold all details, so I will provide some basic best practices.
- Please think about your network and deployment configuration.
- Having a Domain Controller in the cloud should be considered (and you will see in later documentation that it will be recommended). See http://msdn.microsoft.com/en-us/library/windowsazure/jj156090.aspx#BKMK_Scenarios.
- You will need to utilize a local SQL Server on the same Azure Virtual Machine.
- We have not tested,and do not intend to test, running SQL Server on a different server.
- Using SQL Azure is not supported due to architectural differences.
- Understand the cost model. You will be charged for the Azure Virtual Machine, the Storage, the VPN tunnel itself and network traffic.
- Not all workloads and scenarios will make sense to run in Azure IaaZ.
- Support for FIM on an Azure VM is via the FIM Support Team and not Azure.
- FIM 2010 R2 SP1 and later is supported on the IaaS
Please email Tim Macaulay
- MSRESOURCE: http://blog.msresource.net/2013/04/16/fim-and-azure-infrastructure-as-a-service-iaas/
- KAUSHAL’S BLOG: http://blogs.technet.com/b/identity_and_data_protection/archive/2013/04/18/forefront-identity-manager-fim-2010-r2-sp1-is-now-supported-on-azure-iaas-vms.aspx
- FIMSPECIALIST: http://www.fimspecialist.com/fim2010-r2-sp1-now-supported-on-azure-iaas-idmaas/