Azure Services Platform .NET Services

1. This presentation incorporates some content and demos from Microsoft Azure Services Platform.NET Services

2. Agenda • Overview of .NET Services • Quick Tour of .NET Services Portal • Explain and Demo: Service Bus • Explain and Demo: Workflow Service • Explain and Demo: Access Control Service

3. .NET Services and the Azure Platform Azure™ Services Platform

4. .NET Services - 3 Key Services .NET Services • Service Bus • Communication relayed through the cloud • Workflow Service • Workflow running in the cloud • Access Control Service • Web and enterprise security made easy ServiceBus WorkflowService Access Control

5. Quick Tour of .NET Services Portal

6. .NET Services ServiceBus WorkflowService Access Control .NET Services Service BUS

7. Service Bus - Overview • Service Bus makes it easy to connect applications together over the Internet • Why it exists – to solve these challenges: • Want to make it easy and secure for partners to communicate with your application • Don’t always know the characteristics or scale of the integration • Partners / customers / users have devices and services running behind firewalls, NATs • Microsoft’s Approach • Provide a high-scale, highly-available “Service Bus” that supports open Internet protocols

8. Service Bus – Key Points • Services that register on the Bus can easily be discovered and accessed, across any network topology • The Service Bus provides the familiar Enterprise Service Bus application pattern • Helps to solve some of the hard issues that arise when implementing this pattern across network, security, and organizational boundaries • Internet-scale

9. Service Bus - Application Pattern

10. Service Bus – Service Registry

11. Service Bus - Connectivity • Relay • Ensure applications connect • Available to all via the service registry • Direct connect • Uses the relay to establish communication • Then shortcuts for efficiency • Publish-Subscribe • Builds on the relay and direct connect connectivity capabilities • Available via HTTP / REST / ATOM • Available in .NET via WCF Bindings

12. Service Bus – Relay Connection

13. Service Bus – Direct Connection

14. Service Bus DemoDemo 1 – Echo

15. Service Bus – Multicast Publish/Subscribe

16. Service Bus DemoDemo 2 – Multicast

17. Service Bus - Summary • Service Registry • Relay and direct connect connectivity • Publish/Subscribe • Integrated with Access Control Service

18. .NET Services ServiceBus WorkflowService Access Control .NET Services WORKFLOW Service

19. Workflow Service - Overview • Workflow Service is a high-scale host for running workflows in the cloud • Why it exists – to solve these challenges: • Want to easily describe long-running processes • Want modularity and nesting • Easy to describe but in practice harder to run • Microsoft’s Approach • .NET 3.0/3.5/4.0 addresses key developer requests • .NET Services makes it easy to deploy, manage and run workflows

20. Workflow Service – Key Points • Workflow Service provides: • A set of activities optimized for sending, receiving, and manipulating HTTP and Service Bus messages • A set of hosted tools to deploy, manage and track the execution of workflow instances • A set of management API’s • Workflows can be constructed using the familiar Visual Studio 2008 Workflow Designer

21. Workflow Service – Key Points Offers Scalable, Lightweight Service Orchestration Declaratively configure activities that manage + control service interactions • Easy to Define • Define activities to send + receive messages and inspect XML • Easily define Microsoft .NET Framework activities for control flow • Easy to Design • Just drag and drop from predefined activities into Visual Studio Designer • Easy to Manage • Portal + APIs make it easy to deploy, manage running workflow instances • Easy to Scale • Internet scale. Supports scenarios of nearly any size and scope. • Increase application performance, thanks to transparent scalability of the service’s underlying components and automatic distribution of loads

22. Workflow Service – Key Points Integrates with Other Services Tightly integrated with other .NET Services • Access Control • The Access Control Service provides authorization functionality • Service Bus • Workflow Service communicates with the Service Bus to support applications that run across organizational boundaries. Leverages Existing Skills The Workflow Service aligns with your existing experience in the .NET Framework • Windows Workflow Foundation (WF)-Based Environment • Workflows designed using Visual Studio, similar to how you design in WF • Workflows are defined in XOML using activities included with WF as well as activities for the cloud platform

23. Workflow Service - Interaction

24. Workflow DemoDemo 3 – Watchdog

25. Workflow Service - Summary • Execute Workflows with high availability • Design Workflows using existing tools • Easily deploy and manage Workflows • Portal for easy access • Management APIs for rich automation

26. .NET Services ServiceBus WorkflowService Access Control .NET Services Access Control Service

27. Access Control Service - Overview Helps you avoid the complicated programming normally required to secure applications that extend beyond organizational boundaries.

28. Access Control Service - Overview • Why it Exists – To solve these challenges: • Many identity providers, many vendors, many protocols, complex semantics – tricky to get right • Applications strewn with one-off access logic • Hard to get right, not agile, not compliant, many dead ends • Approach • Automate federation for a wide-range of identity providers and technologies • Factor the access control logic from the application into manageable collection of rules • Easy-to-use framework that ensures correct token processing

29. Access Control Service – Key Points • Stop tying your apps to a specific security model • Instead, check claims within the application • Enable security scheme external to application • Multiple security schemes can be enabled • Rules used to map claims to what app expects • Integrate with standards-based identity providers, including enterprise directories and web identity systems such as Windows Live ID • .NET Developers use the Geneva Framework

30. Access Control Service – Example Scenario If your customer is reluctant to create and manage thousands of user accounts for an application on your Web site, you can use Access Control Service to federate the customer's existing identity management system. Whether the customer uses Active Directory® service, other directory systems, or any standards-based infrastructure, just configure Access Control Service for it, and your application responds as if the customer’s user accounts were managed locally.

31. Access Control – Interaction 3. Map input claims to output claims based on access control rules 1. Define access control rules for a customer Your Access Control Project (a hosted STS) 4. Send Token (output claims from 3) 0. Certificate exchange; periodically refreshed 6.Claims checked in Relying Party 2. Send Claims Requestor (Your Customer) Relying Party (Your App) 5. Send Message w/token

32. Access Control DemoDemo 4 – Federation

33. Summary: Access Control Service • Flexible, rules-driven access control • Rich support for a wide range of identity providers • The Geneva framework is the .NET developer experience • Easy to incorporate into existing applications • Works with lots of other environments; e.g. Sun’s Java Metro 1.3, …

34. Summary: .NET Services • Makes the cloud enterprise-accessible • Service Bus – cloud-relayed communication • Access Control Service – security made easy • Workflow Service – workflow in the cloud

35. Discussion: .NET Services

36. Resources • Azure Portalhttp://www.Azure.com • Azure User Group Sitehttp://www.AzureUserGroup.com • Azure Blogshttp://www.AzureFeeds.com