Microsoft Media Platform: Guidance on Choosing and Migrating

by Tim Ammann

This article offers guidance for choosing among the Microsoft Media Platform Technologies that deliver video content. It includes general guidance for migration, and provides details about the new Windows Azure Media Services platform.

Technical Reviewers: John Deutscher, Cenk Dingiloglu, David Bristol, Kilroy Hughes, Steven Goulet

Also thanks to: Anton Kucer, Eric Zocher

Published: January 2013

Applies to: Windows Media Services, IIS Media Services, Windows Azure Media Services, Expression Encoder, Transform Manager


Microsoft offers a number of important feature-rich Media Platform Technologies that are useful in a wide variety of scenarios. Nevertheless, some of the technologies offer advantages over others for particular scenarios. This article offers guidance for choosing among them and considerations for migration, including a look at the revolutionary new Windows Azure Media Services platform.

1 Platform Technologies

Two Microsoft Media Platform Technologies are on-premises (that is, they run on servers placed directly in an enterprise), while the latest, Windows Azure Media Services, is cloud-based as part of Microsoft's Windows Azure cloud computing platform (

On-premises media technologies:

Cloud-based media technologies:

The initial components of Windows Azure Media Services, including Ingest, Encoding, Content Protection, and On-Demand, are available or shipping soon. Advertising (Ad Insertion) is currently available through Client SDKs. Additional components, including Live Streaming and Analytics, will be rolled out as they become available. When all of the components are in place, Windows Azure Media Services will offer a complete end-to-end media services solution, including video ingest, encoding and conversion, content protection, on-demand streaming, live streaming, and analytics.

2 Encoding and Conversion Technologies

The following encoding and conversion technologies are available from Microsoft:

  • Transform Manager 1.1 : Converts media files to on-demand smooth streaming format for Silverlight clients and Apple mobile digital devices. This product is available for free download.
  • Expression Encoder 4 with Service Pack 2 : Expression Encoder is a video-encoding and live-broadcasting application. A free version is available. The Expression Encoder 4 Pro version is necessary for H.264 encoding. Some SP2 features, such as GPU encoding and live template support, are also available only in Expression Encoder 4 Pro.


Expression Encoder 4 Pro will be unavailable for purchase after 12/31/2013. For more information, see Microsoft Expression Changes. Additional encoders are available from Microsoft partners such as Telestream, Digital Rapids, Harmonic, Elemental, and Envivio.

  • Windows Azure Media Encoding Services: Incorporates the technologies of Transform Manager and Expression Encoder into the Windows Azure cloud. Going forward, the latest versions of these technologies will continue to be developed in the Windows Azure Media Services cloud.


Third-party encoders are also available for IIS Media Services. For more information, see the Partners section of the IIS Media Services page. For Windows Azure Media Services, third-party encoders will be available in the Azure Store sometime after Windows Azure Media Services releases.

3 Recent History of Media Formats

The Windows Media format helped establish internet video download, first to PCs, then to other devices by using the WMV file container, WMA audio codecs, and the VC-1 video codec (and its predecessors).

To support large scale adaptive bitrate streaming over the internet, Microsoft later developed Smooth Streaming. Smooth Streaming uses the PIFF media format (Protected Interoperable File Format), which is derived from the MPEG ISO Base Media File Format standard. The PIFF media format supports the MPEG AVC video codec, AAC and other audio codecs, and PlayReady DRM.

Recently, the core technologies in PIFF and Smooth Streaming have been incorporated into the MPEG standards called Common Encryption (ISO/IEC 23001-7) and DASH "Dynamic Adaptive Streaming over HTTP" (ISO/IEC 23009-1).

Migration to the DASH standard is underway at Microsoft and most of the Internet video industry. The W3C is standardizing the APIs for HTML5 browsers. These APIs will allow Web pages to stream DASH to HTML5 browsers on all types of devices, including TVs, PCs, tablets, and phones.

4 Why migrate from Windows Media Services to IIS Media Services?

If you are currently using Windows Media Services, migrating to IIS Media Services offers the following advantages:

  • The Smooth Streaming format. Smooth Streaming is a form of adaptive streaming over HTTP that stores video on disk as a single full-length file per encoded bit rate, but creates file chunks virtually upon client request. Because the chunks are sent as standalone files, they are fully cacheable via local network HTTP caching or with a downstream CDN (Content Delivery Network). The single file approach combined with dynamic chunking offers both significant adaptive performance and file-management benefits.
  • IIS Media Services can stream to mobile devices, including Apple and Android clients.
  • IIS Media Services can stream AVC video in ISO Media files to clients, including Silverlight. (Windows Media Services cannot stream AVC video in ISO Media File Format).
  • IIS Media Services can push a live stream from an encoder to multiple downstream media servers. IIS Media Services 4.1 has the ability to pull or push from an upstream server to a downstream server. With Windows Media Services, you are limited to a single downstream server.
  • IIS Media Services is supported on Windows Server 2012, while Windows Media Services is not. Take this into consideration when migrating to Windows Server 2012.

Scenarios still appropriate for Windows Media Services

Re-encoding requirement

IIS Media Services does not support the wmv video format, so wmv files must be converted to Smooth Streaming (fragmented ISO Media) format. When planning a migration, take into consideration the size and number of files to be converted.

For more information on re-encoding content for IIS Media Services, see the section "Re-encode wmv content" later in this document.

Multicast Streaming (Multicasting)

Multicast streaming is a feature of Windows Media Services that lets you deliver streaming content on a closed internal network from a media server. Multicast streaming uses special multicast-enabled routers to deliver streams to an IP address that all clients subscribe to. For more information about multicast streaming, see Delivering content as a multicast stream.

As of this writing, multicast streaming is supported by Windows Media Services, but not by IIS Media Services or Windows Azure Media Services.

Audio-only streaming

If you are streaming audio-only content, Silverlight does not support audio-only smooth streaming from IIS Media Services. Silverlight requires a stream to contain both audio and video. For this reason, Windows Media Services may be the better choice for audio-only scenarios.


If you must use Silverlight, Expression Encoder and IIS Media Services to stream audio, there is a workaround: you can provide Expression Encoder with a very low bitrate (for example, 10 bits per second) placeholder video stream that contains a 1 x 1 pixel. Although not a true audio-only stream, the video portion of the combined audio/video will be very minimal.

5 Reasons to use IIS Media Services and Windows Media Services side-by-side

In some scenarios, it might be appropriate to use IIS Media Services and Windows Media Services side-by-side, with each having separate, specific purposes. Because IIS Media Services and Windows Media Services are separate technologies, they can coexist on the same computer.

For example, if you have a mix of audio and video formats, you could use Windows Media Services to deliver wmv and audio content, and IIS Media Services to deliver Smooth Streaming content to Silverlight clients and mobile devices. If you need to stream content both internally and outside to the web, you could use Windows Media Services for multicast streaming, and IIS Media Services for smooth streaming.

The following table shows a comparison of the live streaming features in Windows Media Services and IIS Media Services:

Streaming: Windows Media Services vs. IIS Media Services 4.1

Streaming Feature WMS 2008 IIS MS 4.1
Archiving of live streams
Broadcast streaming from files
High Availability content sourcing (encoder failover)
HTTP Streaming
Multiple bitrate streaming (Intelligent vs. Smooth)
Server and client side logging
Unicast HTTP streaming from live encoders
Play While Archiving (late joiner feature)
Advanced Server-side Playlists
Multicast streaming
Windows Media Services proxying and caching
Full Network DVR
ISO-based file formats
Low-latency streaming
REST-based streaming requests
Standard HTTP proxying and caching
Streaming to iOS clients
Streaming to mobile devices

6 Considerations when migrating to IIS Media Services

When migrating from Windows Media Services to IIS Media Services, a phased, gradual approach can be taken, using these three steps:

  1. Change the encoder.
  2. Install Silverlight, or use the Microsoft OSMF plugin.
  3. Re-encode wmv content.

1) Change the Encoder

The mainstream support end date for Windows Media Encoder was 12/01/2010, so if you are currently using Windows Media Encoder, switch to either using the stand-alone Expression Encoder tool or a third-party encoder.


Expression Encoder 4 Pro will be unavailable for purchase after 12/31/2013. For more information, see Microsoft Expression Changes. Additional encoders are available from Microsoft partners such as Telestream, Digital Rapids, Harmonic, Elemental, and Envivio.

Replacing the encoder is the first step because the encoder is perhaps the easiest of components to replace. Expression Encoder can create content for both Windows Media Services and IIS Media Services.

2) Install Silverlight, or use the Microsoft OSMF plugin

Depending on your requirements, your next step will be to install Silverlight on your clients, or use the OSMF plugin to prepare to Smooth Stream to Flash.


If your clients are currently using Windows Media Player, you can install Silverlight on all your clients. Silverlight is capable of playing content from both IIS Media Services and Windows Media Services.

In this interim step, you will have two different Silverlight Application (xap) client files: one for Windows Media Services, and one for IIS Media Smooth Streaming. At this point, you are still using Windows Media Services, but your clients are ready to receive Smooth Streaming content when you make the transition to IIS Media Services. In addition, this interim step has the advantage of providing wider support for browsers, including Safari.


Different Silverlight applications (.xap files) are required for playing back IIS Media Services and Windows Media Services content. To play Windows Media content, a number of Silverlight templates are available as part of the installation of Expression Encoder. For playing Smooth Streaming content, you can use the Microsoft Media Platform Player Framework.

OSMF (Open Source Media Framework) plugin

If you do not need to use DRM such as PlayReady and are restricted from deploying Silverlight in your Enterprise, you can use the Microsoft Smooth Streaming plugin for Open Source Media Framework. After your .wmv content has been re-encoded to Smooth Streaming format, the plugin will allow you to deliver that content in Smooth Streaming format to Flash clients.


The OSMF plugin cannot deliver content that is in .wmv format.

In this interim step, your clients will continue using Windows Media Player for Windows Media Services. After your re-coding is complete, you can transition to using IIS Media Services and the OSMF plugin to stream to Flash clients.

A few details about the plugin

The Microsoft Smooth Streaming plugin for Open Source Media Framework 2.0 can easily add Smooth Streaming playback capabilities to existing OSMF-based players. The plugin can be dynamically loaded for use with Strobe Media Playback. With very little coding, the plugin can enable your new or existing applications to consume Smooth Streaming content.

The plugin has the following features:

  • On-demand Smooth Streaming playback (Play, Pause, Seek, Stop)

    • Support for video codecs - H.264
    • Support for Audio codecs - AAC
  • Multiple audio language switching with OSMF built-in APIs

  • Maximum playback quality selection with OSMF built-in APIs

This version of the plugin requires OSMF 2.0 and Adobe Flash Player 10.2 or higher. For more information, see the Microsoft Smooth Streaming Plugin for OSMF (Preview) download page.

3) Re-encode wmv content

When re-encoding your wmv files for migration, you'll need to choose an appropriate Smooth Streaming format and decide which re-encoding tools to use. After you are done re-encoding, change your application and web page links to use the Silverlight Smooth Streaming client or OSMF player.

The IIS smooth streaming format

The IIS Media Services Smooth Streaming format consists of .ismv files that can contain H.264, or VC-1 compression formats. For more information, see IIS Smooth Streaming Technical Overview.

If your goal is to stream to mobile devices, it is recommended that you choose H.264 rather than VC-1 as the target format because the H.264 format is supported by the hardware decoders on most mobile devices as well as the GPU decoders on most PCs.

Re-encoding options

To do the re-encoding, Microsoft offers three choices:


Expression Encoder 4 Pro will be unavailable for purchase after 12/31/2013. For more information, see Microsoft Expression Changes. Additional encoders are available from Microsoft partners such as Telestream, Digital Rapids, Harmonic, Elemental, and Envivio.

Windows Azure Media Encoder puts the functionality of Expression Encoder into the Windows Azure Media Services cloud. Going forward, the encoding technology in Windows Azure is the one that Microsoft will continue to develop.

If you do decide to use Transform Manager, keep in mind that the Windows Azure equivalent of Transform Manager (that is, the format conversion service on Windows Azure Media Services) will continue to evolve in the cloud while the downloadable version is likely to undergo only minor changes and have limited support.

OS Platform Considerations

When migrating to IIS Media Services, it is possible to do an in-place migration on the same server, migrate to a separate server, or migrate to virtual machines.

Many customers use virtual machines to reduce the TOC (total cost of ownership) and maximize the use of their hardware. Of course, if you migrate to Windows Azure Media Services, you will be able to take advantage of the scalability of the Azure cloud without the overhead of maintaining an in-house infrastructure.

An on-premises hybrid approach

One hybrid, less compute-intensive approach is to produce only your new content in Smooth Streaming format, and maintain your existing content in the older wmv format. The content could be served by using IIS Media Services and Windows Media Services side-by-side, as mentioned earlier in this document. This scenario might be an option if your older content is less frequently accessed, or used exclusively by legacy clients.

Choose a format that supports dynamic packaging

If your plan is to migrate at some point to Windows Azure Media Services for on-demand streaming, your best choice will be to use either the Smooth Streaming or multi-bitrate ISO Base Media File Format (Smooth Streaming is itself a fragmented ISO Base Media format), for the following reasons:

  • Fragmented ISO Base Media (fMP4) offers substantial technical advantages over HLS. For more information, see Unifying Global Video Strategies: MP4 File Fragmentation For Broadcast, Mobile and Web Delivery.
  • The Windows Azure Media Packager can easily repackage between Smooth Streaming and multi-bitrate ISO Base Media formats.
  • The Windows Azure Media Services Origin Service allows you to use a single Smooth Streaming or ISO Base Media 14496-12 multi-bitrate source to dynamically serve both Smooth Streaming and HLS clients. This feature, called dynamic packaging, avoids the need for you (or for Windows Azure) to duplicate storage for every streaming-format type (for example, MP4 for HTML5; Smooth Streaming for Silverlight, XBox, and Flash; and MPEG2-TS (MPEG 2 Transport Stream, also called M2TS) for HLS to iOS devices). As a result, you only need to store and pay for the files in one storage format. For more information, see Walkthrough: Dynamically Packaging Assets.

A note on MPEG-DASH

MPEG-DASH (MPEG Dynamic Adaptive Streaming over HTTP) is a standard for dynamic adaptive bit-rate HTTP streaming that will be fully supported in Windows Azure Media Services. Support will also be added to the Microsoft Media Platform Smooth Streaming client development kits. For more details, see Microsoft Announces Support for MPEG-DASH in Microsoft Media Platform .

The adoption of MPEG-DASH will greatly reduce (and hopefully eliminate) the need for re-encoding between competing video formats. After it is fully supported in Windows Azure Media Services, MPEG-DASH will become Microsoft's preferred format for HTTP streaming.

If you currently stream using Windows Azure Media Services using multi-bitrate ISO Base Media or Smooth Streaming formats, you will not need to repackage or re-encode your video to MPEG-DASH. Windows Azure Media Services will do this for you dynamically. For this reason, Microsoft recommends that when choosing to encode, you use either the Smooth Streaming or multi-bitrate ISO Base Media format.

7 The Advantages of Migrating to Windows Azure Media Services

The current environment for video streaming is experiencing new challenges. The video portion of Internet traffic today is significant and growing rapidly, as is the number of internet connected TVs and mobile devices. In this environment, video providers and broadcasters are switching to IP as the medium of choice to reach this wide diversity of endpoints.

To address these challenges, Windows Azure Media Services is designed to become a one-stop platform for securely encoding, packaging, and delivering video content from Windows Azure or CDNs, thus offering the scalability and reach of the cloud.

Some of advantages of migrating to Windows Azure Media Services are:

  • Windows Azure Media Services has the scalability and reliability of a cloud platform and can handle large bursts in demand for video applications.

  • It is widely available for a global audience and can use third-party CDNs like Akamai, Level3, or Limelight.

  • Windows Azure Media Services has cloud-based versions of familiar Microsoft Media Platform and media partner technologies.

  • As a Platform-as-a-Service (PaaS), Windows Azure Media Services is faster, cheaper, and lowers risk:

    • PaaS is faster because there is less work for developers. End-to-end solutions benefit from a single platform that solves integration issues. As a result, applications can go from idea to availability more quickly.
    • PaaS is cheaper because it offers less administration and management overhead, and greater economies of scale: you pay only for what you use, and large capital outlays for media servers and network infrastructure can be replaced by the more efficient operating expenses of cloud computing.
    • PaaS lowers risk. Because the platform does more for you, there are fewer opportunities for error.
  • Security Standards and Certifications: Windows Azure Media Services Security is working towards SOC2 (Service Organization Control 2) compliance and plans to complete a CDSA (Content Delivery and Security Association) certification process and an MPAA audit in 2013.

Windows Azure Media Services Usage Scenarios

Windows Azure Media Services have the flexibility and power to enable you to create whatever media services solution that you envision. Some key usage scenarios are:

  • Creating an end-to-end workflow in the cloud. For example, a content management service can use Windows Azure Media Services to process on-demand Smooth Streaming video and distribute it to a variety of mobile and desktop clients.
  • Developing hybrid workflows that incorporate pre-existing on-premises resources. For example, a video production house might upload its finished videos to Windows Azure Media Services for encoding into multiple formats, and then use the Windows Azure Media Services Origin Service and a third-party CDN to deliver video on demand.
  • Choosing to utilize built-in Media Services components, or mixing and matching your own custom components or components from third parties. Individual Windows Azure Media Services components can be called via standard REST APIs for easy integration with external applications and services.

The following section provides a more detailed breakdown of the various Windows Azure Media Services components.

Principal Windows Azure Media Components

Windows Azure Media Services components, when put together, are designed to create a complete end-to-end workflow. Currently available components include Ingest, Encoding and Conversion, Content Protection, On-Demand Streaming, and client-side support for Ad Insertion. Forthcoming components are Live Streaming, Analytics, and Identity Management. These components are described in more detail below.

Secure Media Ingest Service

The Windows Azure Media Services Ingest service uploads video via HTTPS into Windows Azure Blobs for processing or delivery. A few key points:

  • When uploading high value content such as studio quality mezzanine files, you should pre-encrypt the files with AES 256 prior to upload. The Media Services .NET SDK and Java SDK support this pre-encryption, which is a best practice for compliant secure media workflows.
  • For greater efficiency when uploading your videos, you can use a fast upload UDP technology such as the one from Aspera, which can be obtained through the Azure Store.
  • If your solution requires support for bulk ingest, you can implement this using the Media Services REST API, or the .NET or Java SDKs.

Encoding and Conversion Service

Windows Azure Media services can encode to and convert a variety of video and audio formats. The functionality of the standalone Expression Encoder tool has been folded into Windows Azure Media Encoder, which will continue to be Microsoft's primary encoding offering.

Windows Azure Media Encoder:

Content Protection

Content Protection is a feature of Windows Azure Media Services that provides encryption and digital rights management. Some of the features available or planned are:

Content protection solutions from partners like BuyDRM, EZDRM, and Civolution are also available for solutions with Windows Azure Media Services.


To use PlayReady, you currently need to provide your own PlayReady server or use one from a third party provider such as those mentioned.

On Demand Streaming

Windows Azure Media Services offers an Origin Service that delivers Video on Demand.

The Origin Service is a managed adaptive bitrate streaming service that offers guaranteed bandwidth, auto recovery, high redundancy, and high availability. You can use the Origin Service in conjunction with third-party CDNs like Level3 and Akamai to provide wide availability and low latency.

The Origin Service offers dynamic packaging support of standard MP4 files into Smooth Streaming, MPEG-DASH, or HLS files. This means that a file in one format can be packaged on-the-fly and delivered in the other format. This eliminates the need to store two separate versions of the same file, greatly reducing storage and CPU costs.


The dynamic packaging feature does not apply to MPEG 2 Transport Stream (M2TS) files, or to encrypted files.

Live Streaming

Live Streaming is a forthcoming feature of Windows Azure Media Services that will offer live ingest, live origin, and live encoding that will enable video to be streamed for live events.

Windows Azure Media Services Live Streaming was previewed with great success in the 2012 Olympics. Here are some highlights of its features:

  • One source, many clients: using industry standard H.264 and AAC codecs, content was encoded once and delivered to all devices and platforms, including Silverlight, Flash, iOS, Android, and Windows Phone clients and devices.
  • Easy configuration and automation: Live and on-demand channels were established and configured with a few lines of code. The creation of 140 live HD channels was automated. No manual setup or steps were required. For example, 120 channels were initially provisioned. When it became clear that 20 additional channels would be required, with a few clicks, the 20 channels were added and available within the space of 30 minutes.
  • Scalable, reliable, robust: During the 2012 Olympics, Windows Azure Media Services provided a scalable mechanism that handled spikes and prioritization of high volume transcoding needs. A solution for an event like this would have been unachievable or too costly with traditional on-premise implementations or generic cloud compute services. Redundant ingest, origin, storage and edge caching services across multiple datacenters delivered a high availability solution that provided automated self-healing when issues arose.
  • Real-time monitoring: The REST channel APIs provided by Windows Azure Media Services were used to build a web-based dashboard that allowed broadcasters to monitor the health and quality of the outbound flow of streams to CDNs.
  • Seamless transition between Live and Video On-demand: Video was available immediately for replay both during and after a live broadcast with full DVR functionality. As an event ended in real time, a full video on-demand archive was created.
  • Microsoft Media Platform tools: Microsoft provided rough cut editing tools for highlight reel creation. Within a couple of minutes of an event, these tools allowed highlight clips to be quickly assembled into highlight reels that could be streamed from the live chunks already cached at the CDN edge. There was no need to download or save the video assets locally.
  • Automated conversion of content: Using the VOD Services SDK, several custom media processing tools were created for the automatic conversion of content to various formats that could be served to a wide variety of devices and online services.

For more information about how Live Streaming was implemented in the 2012 Olympics, see Windows Azure Media Services and the London 2012 Olympics.

During the calendar year 2013, the above Live Streaming capabilities are to be gradually added to Windows Azure Media Services, becoming available for general consumption as they are released.

Currently, you can live stream using IIS Media Services 4.1, or use the facilities of third party providers. A new version of IIS Media Services is planned but has not yet been released.

Advertising (Ad Insertion)

Ad Insertion is currently available in client SDKs, with support for the VMAP and VPAID standards in clients using MMPPF, PlayerFramework, OSMF AD plugins and the Windows Azure Player Framework for iOS.

On the server side, ad integration features are forthcoming.

Analytics and Identity Management

Analyticsand Identity Management are forthcoming features of Windows Azure Media Services.

  • Analytics refers to tracking the penetration and usage of video content. Real-time analytics are planned.
  • Identity Management already exists in Windows Azure but will be extended to Media Services to provide access control for your applications.

Windows Azure Media Services Pricing

Windows Azure Media Services charges for storage, compute cycles, and egress of data (that is, to download the content or serve it). There is no charge for uploading content to Azure unless you are using a third-party fast transfer tool such as the one from Aspera. The compute cycles relate mostly to encoding. Regular Windows Azure Storage costs apply to storage.

Preliminary summary information about how Encoding and On-Demand services will be charged is provided below. For up-to-date, detailed pricing information for Windows Azure and Windows Azure Media Services, see Windows Azure Pricing Details.

Depending on your scenario, the total cost of serving your content through Windows Azure Media Services can be significantly less than that of streaming from your own in-house infrastructure.


Encoding is charged by the total number of gigabytes input to and output from the encoder per billing-cycle month. (The total of gigabytes processed is the data input to the encoder, plus the data output from the encoder.) Both input and output data are stored in your Media Services storage account, for which the standard Windows Azure Storage and Data Transfer charges apply.

To ensure that specified number of encoding tasks can run concurrently, you can purchase one or more encoding reserve units (RUs). One reserve unit can run one task at a time. A typical number of encoding reserve units is from 1 to 5. A reserve unit is also the primary unit of SLA (Service Level Agreement). If you do not purchase reserve units, the level of service that you receive cannot be guaranteed.

More details are available on the pricing page.

On-Demand Streaming

Once On-Demand Streaming becomes generally available, you will need to purchase reserved units to use the service. On-Demand Streaming will be billed based on the number of reserved units in use calculated on a daily basis using the highest number of reserved units that were active in the account in the corresponding 24-hour period. The allocated bandwidth per On-Demand Reserved Unit is 200 Mbps. More details are available on the pricing page.

Scenarios still appropriate for earlier Media Services versions

In some scenarios, Windows Azure Media Services might not be the best choice. For example, this might be the case if multicasting is a requirement, if heavy traffic or the need for scalability is not a concern, or if a Windows Azure Media Services component that you require has not yet been released. Note, however, that in many cases third parties can supply components for Windows Azure Media Services that have not yet been made public.

Alternate or Hybrid Solutions

You might think that an interim approach to streaming from Windows Azure would be to host IIS Media Services in an Azure Web Role. Although this might make moving an existing IIS Media Services solution to the cloud seem more straightforward, it has the following drawbacks:

  • Because Web Role VMs are not persistent, you would have to store state and session data on an Azure Drive via Windows Azure Storage Services.
  • Live streams would not be archived; you would have to implement this functionality yourself. Windows Azure Media Services Live Streaming, when available, will do this for you automatically.

If your existing on-premises infrastructure is sufficient for most cases but is occasionally overwhelmed by 'bursty' traffic or events, you might consider offloading the extra traffic onto a CDN such as those offered by Akamai, Level3, or Limelight.

Programming Windows Azure Media Services


All of Windows Azure Media Services is accessible through REST APIs, which are built on OData 3.0. Because it uses HTTP, the APIs will work with any platform and any device. You can program the REST APIs directly or through the .NET or Java SDKs.

The .NET and Java SDKs conveniently wrap the REST APIs to make coding your solutions easier. For more information, see Building Applications with the Media Services SDK for .NET. To download the .NET SDK for Windows Azure Media Services, see Windows Azure Media Services .NET SDK (Preview).

To make direct REST API calls rather than using an SDK, or to use programming languages outside of the .NET Framework, use the Media Services REST API. For more information, see Building Applications with the Windows Azure Media Services REST API.

Smooth Streaming Client SDKs

Smooth Streaming Client SDKS are available for a wide variety of platforms, including Windows 8, Silverlight, Windows Phone, iOS, and Android. Some are available from third parties. For more information, see Media Services Client Development.

Media Platform Player Framework

The Microsoft Media Platform Player Framework is a fully open source video player for Silverlight, HTML5, Windows Phone, Xbox, and Windows 8 applications. For more information, see Microsoft Media Platform Player Framework.

Xbox LIVE Application Development Kit (ADK)

The Xbox LIVE Application Development Kit (ADK), available to Xbox Partners, can be used to create applications that consume media content from Windows Azure Media Services and IIS Media Services. The ADK includes the Smooth Streaming Client for Xbox LIVE ADK, and the Microsoft Media Platform Player Framework for Xbox LIVE ADK.

8 Resources