<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Start with Parse Server on Azure (Managed Services)</title><link>https://www.dotnetzone.gr:443/cs/blogs/ppolyzos/archive/2016/07/09/start-with-parse-server-on-azure-managed-services.aspx</link><description>In our previous article we explored the option of creating, deploying and managing the Parse Server using a pre-configured VM image on Microsoft Azure. In this post we are going to describe an easy way for Parse developers to continue their work on Microsoft</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator></channel></rss>