As a developer I want a set of Quickstarts that illustrate how to apply Enterprise Library to specific aspects of Windows Azure development.

As a developer I want to reliably store the log entries to SQL Azure.

As a developer, I want the data access block to help me accessing the Azure storage by providing TDD-friendly wrappers and interfaces that can easily be passed as dependencies to my own classes, and be able to mock/stub in my unit tests.

As a developer, I want the data access block to help me with paging forward and backward through a result set that comes from azure storage tables.

As a developer, I want to leverage the built-in transaction support in Windows Azure table storage by storing multiple entity types in the same table and/or use a compensation mechanism to ensure consistent updates across multiple tables.

As a developer, I want to have programmatic configuration support via fluent interface for the rulesets and auto-scaling operations.

An API/ framework that makes it easy to implement multi-tenancy in a Windows Azure application. Not only from a code standpoint of view, but also a multi-tenant database.

As a developer, I would like to have an API to backup and restore selected tables and databases.

As a developer I want to load my Enterprise Library configuration from a cscfg file.

As an administrator I want to have a policy-based mechanism to purge the entries in the WAD tables so that I can optimize the usage of storage. The policies should consider kind of entry, severity, age, etc.

As a developer I want a reference implementation that is built using a test driven methodology, so I can learn how I can apply test driven development in my own applications.

As a developer, I would like to upload selected folders and files to Azure instead of deploying the full solution to Azure. For example when you need to replace a small image or other resource file.

When paging through data that comes from the azure storage tables, I want the ability to navigate to a specific page.

For complex application, an idea of distributed synchronization mechanism should be implemented. Especially in the case of Enterprise Applications, one would very often need one of N roles to take ownership of a resource (e.g. as a Master Role).

As a developer I want to load configuration information from a web service so that I can keep my configuration on-premises or in a different cloud or in some arbitrary location, not packaged in the look for proper name of unit of deployment.

As a developer I want my log entries stored in Azure Storage to be transferred to a Remote Logging Service (or any other trace listener) based on the number of items OR age OR absolute size so that I could optimize my logging strategy AND archive my log entries to a on-premises data store.

As an administrator, I'd like to correlate the logs generated with the performance counters I collect from the instances through Azure Diagnostics subsystem.

As a developer, I want the data access block to handle page contiuation tokens for me when the server returns less than the expected rows to me. Especially when the query passes over partition boundaries.

As a developer I want to easily forward my log entries to a remote service so that I can reuse my current remote logging service infrastructure.

I need the ability to automatically purge WADLogs to blob storage (hourly or daily - one blob per interval)