No idea; it's a system one so if it's not supported in Azure I would guess there's a reason for that. It may be to avoid performance problems, or possibly it's because it relies on some other feature in SQL Server that's also not present in Azure.