Added readme with text from blog post

Readme.md

@@ -0,0 +1,27 @@
+## Azure Media Services Operations Tool ##
+When building a video solution on Azure Media Services, we may have the following scenarios:
+
+- A customer may choose to build a CMS tool integrated with their existing systems for automated workflows.
+- A system integrator (SI) who helps customers building video solutions based on Azure Media Services may choose to build a packaged SDK or software framework so that such a project does not have to start from zero. This approach speeds up time to market, makes project delivery more repeatable and makes the SI more competitive in the market.
+
+In these situations, what customers/SIs need may not be a stand-alone tool for human, rather a faster way to build a fully integrated solution with automated workflow. The author would like to share a toolset which has been used in such solutions. The code is structured in such a way that it is scenario-based. The value of this toolset is to make the source code available. The source code can be used as sample code, or used directly in a solution or leveraged for design and planning of such a solution.
+
+This is a comprehensive tool set and covers all key areas of Azure Media Services:
+
+- Live
+- VOD
+- Live-to-VOD management and live archive diagnostics
+- PlayReady protection (both live and VOD)
+- AES-128 Encryption (both live and VOD)
+- Ad insertion (for Aventus live encoder)
+- The functionality included in this tool is based on real world solutions/use cases. This tool has been “battle tested”:
+
+### Limitations ###
+This tool does have limitations. The main limitation is its lack of a user-friendly UI. The tool is of Windows console type Visual Studio project (one for live, one for on-demand and the other for ad marker insertion), with a color console custom class for color-coded UI. I personally found the most convenient way to use the tool is to “use Visual Studio as the User Interface” (changing input parameters, compile and run). Of course this requires the user to understand basic C# syntax. The ideal UI would be a web UI backed by the following
+
+- Authentication provided by Azure Active Directory;
+- Multi-tenant so that different customers can use it against their own media services;
+- Hosted as a SaaS in Azure so that there is no need for user to install/setup
+I’m sure this day will not be far.   
+
+ACKNOWLEDGMENT: Special acknowledgment goes to many members of Azure Media Services Team for their help and insights over the years.