We are currently reviewing this for future inclusion on our roadmap. Will update here on status as this progresses.
Thank you for your suggestionAnonymous supported this idea ·
Customers to Microsoft - "We need offline capabilities with sync, like others provide"
3 years later - 'no, go use Firebase'.
Seriously, it doesn't matter how well you can scale CosmosDB if it doesn't support widely required basic functionality.
99% of cutting edge projects and tutorials out there are ignoring Microsoft. They never even mention anything Microsoft, apart from 'not supported in IE11 / Edge'. You are losing ground rapidly.
"This is not in our current backlog. However, we are constantly evolving and adding more features."
So basically, the Microsoft advice is 'use a competitors product that supports what is generally considered to be a must have feature, because we wont implement it',
So, once again I am pushed away from Cosmos DB to Firebase.
It's becoming increasingly difficult to recommend Azure to my clients.
More and more, Microsoft seem to be giving up on leadership, and are losing ground to even relative newcomers such as Google Cloud Platform.
Offline sync is a no-brainer in a world where mobile first is taken for granted. How can Microsoft preach mobile-first, but then not provide the features in Microsoft products to actually support it, leaving developers no option but to go elsewhere?
There are some very strange decisions being made at Microsoft these days.
Turns out we just had to upgrade the Compute module to 2.3.0: https://www.powershellgallery.com/packages/AzureRM.Compute/2.3.0
Who knows why a newly created Automation account would include an outdated module and would require a manual upgrade :-(Anonymous shared this idea ·
This is not on our roadmap at this time. Will revisit in the future.
Thank you for your suggestion.