1 Azure Solution Alignment Workshop12/20/2017 5:58 AM Azure Solution Alignment Workshop Module 5b: Compute PaaS © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2 How to Present this SectionYour primary goal is to help customers: Understand the concepts around compute PaaS in an Azure architecture Allow customers to understand the components of PaaS to support the solution they are looking to deploy DELETE THIS SLIDE BEFORE DELIVERY

3 Azure Platform-as-a-Service Overview12/20/2017 5:58 AM Azure Platform-as-a-Service Overview © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4 Microsoft Azure Compute (PaaS)12/20/2017 5:58 AM Microsoft Azure Compute (PaaS) A primary goal of PaaS is to remove the need to manage the underlying virtual machine. This allows customers to focus on the real value of the application, which is the functionality that it provides, not the underlying operating system or virtual machine. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5 12/20/2017 Compute IaaS and PaaS Many Organizations require a transition to adopt a fully outsourced model Lines of division between IaaS and PaaS responsibilities are blurred in applications which use both constructs While PaaS is typically the goal, IaaS is a current reality most workloads both require and understand for some functions Both Azure’s IaaS and PaaS capabilities and services can support a wide range of customer applications and services. Cloud Infrastructures can be comprised of on-premises customer or partner hosted and publicly hosted cloud computing thus allowing organizations to consume natively and across their models in a hybrid capacity. © 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6 PaaS Considerations Deploy Manage LimitsUnderstand Tradeoffs and decision points on the following: Upgrade Domains Deployment Slots Web Deploy Continuous Integration Deploy Understand the methods of monitoring PaaS workloads: IIS Logs Azure Diagnostics IIS Failed Request Logs Windows Event Logs Manage Performance Counters Crash Dumps Custom Error Logs .NET EventSource Manifest based ETW Application Insights Auto Scaling: The application environment does not automatically increase or decrease role instances for increase or decrease in load Load Balancing: Application instances not load balanced by default Density: Service Management total cloud services per subscription is 20 Limits

7 Compute

8 Cloud Services Cloud Services, in the context of PaaS, are the units of deployment that contain the roles and instances which comprise a given application. The cloud service will bind to the virtual IP (VIP) that services requests and load balance requests over underlying role instances.

9 12/20/2017 Cloud Services Model It is best to understand what Cloud Services represent. At its simplest form, a Cloud Service is a container or package wrapper for applications that are deployed in Azure. This cloud service model follows the traditional client application deployment model such as the appx format by modern Windows Applications. The target and core idea is to build, version, and deploy the service package unit (cloud service). Thus making it easier for the DevOps or release management team to deploy updates to the cloud service application, as well as, rollback unforeseen side effects from an application update. Scaling cloud services in the PaaS model is trivial, as the application and service definition are both wrapped in a package. Deploying more instances is simply a matter of telling the Azure fabric how many instances you want. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10 Cloud Services Decisions12/20/2017 Cloud Services Decisions Place all assets in cloud services, including code and other installations required to run the application. Everything must be included in the cloud service package and scripts installation. Mandatory Consider the deployment models that will be given when updating the application. There exist a few options, so it’s important to understand the pros and cons Recommended Consider the ability of multiple running deployment models for your cloud service. It’s possible to have multiple deployments in the form of production, test, and staging. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11 Web and Worker Roles It’s important to remember that this type of PaaS application (web and worker roles) have dedicated underlying virtual machines per instance. Typically this is transparent, but it’s particularly important from a diagnostics perspective. Application Type Description Web Role This role is used primarily to host and support applications that target IIS and ASP.Net. The role will be provisioned out of the box with IIS installed and can be used to host front end web based applications. Worker Role This role is used primarily to host and support service type applications. These applications target backend processing workloads. These can be long running processes and can be thought of as Windows Services in the cloud.

12 Web and Worker Roles Model12/20/2017 Web and Worker Roles Model Consider using web and worker roles as follows: Web Roles Tailored for IIS based applications. Configure the scale unity for the instance and ensure that multiple (at least 2) are used for production workloads. Performed by setting the configuration in the service definition. Worker Roles Tailored for service type applications (non-web based). As such, error handling that would be required for a “lights out” service type application should be employed. If the exceptions are not handled in the service inner loop, the role instance will be restarted, causing downtime for processing. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13 Web and Worker Roles Decisions12/20/2017 Web and Worker Roles Decisions Decide on the amount of instances for web and worker roles. Web and worker roles require at least two instances to provide fault tolerance for the automatic maintenance nature of PaaS Mandatory Consider web and/or worker roles if the application requires installation of binaries on the web or application server. Recommended Understand that Virtual Networking is common to allow the communication needed for databases, management services, and other services but it’s not a hard requirement for deploying web or worker role applications. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14 Azure Batch Azure Batch is a service offering that came later in the platform evolution and offers a similar type service, but with a unique twist. It has been designed to run background processes but more centered around Big Data and high performance data. Azure Batch is comprised of two primary components. Azure Batch and Azure Batch Apps. Azure batch APIs focus on the ability to create pools of virtual machines and define work artifacts (work items) that will be scheduled for processing.

15 Azure Batch Decisions Mandatory Recommended Optional12/20/2017 Azure Batch Decisions Define pool of VMs that will perform the underlying work for Azure Batch Jobs Mandatory Analyze the workload to determine which model is the better fit, Azure Batch or Azure Batch Apps. Recommended Leverage the REST API to output monitoring and telemetry to existing systems. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16 12/20/2017 Azure Batch Models Consider Azure batch for workloads in which an existing process or executable is used to process the data. To maximize effectiveness, the data should be in a format that can allow parallelization (cut the data in several chunks). Azure Batch: Create pools of VMs and define work artifacts (work items) that will be schedule for processing. Azure Batch brings with it an API to support the infrastructure. No need to manually build servers and software libraries to handle job scheduling. Azure Batch Apps: Azure Batch Apps take Azure Batch a step further. The goal is to publish an “app” that is essentially a service that will allow data to be fed to it, and it will run as needed. New ability to monitor the jobs through the portal and REST APIs is provided. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17 Service Fabric Service Fabric provides comprehensive runtime and lifecycle management capabilities to applications composed of microservices. It hosts microservices inside containers that are deployed and activated across the Service Fabric cluster. Just like an order of magnitude increase in density is made possible by moving from VMs to containers, a similar order of magnitude in density becomes possible when moving from containers to microservices. For example, a single Azure SQL Database cluster, which is built on Service Fabric, comprised of hundreds of machines running ten of thousands of containers hosting a total of hundreds of thousands of databases (each database is a Service Fabric stateful microservice). The same is true of Event Hubs and the other service mentioned above. This is why the term hyperscale can be used to describe Service Fabric capabilities — containers give you high density, while microservices give you hyperscale.

18 Service Fabric Decisions12/20/2017 Service Fabric Decisions Mandatory You must self-host your application/services. For a Web API, this typically means self-hosting in something like OWIN. Recommended When using partitions, spend extra time understanding the most appropriate way to evenly disperse the data across the partitions, then choose an appropriate partitioning key. Optional Try it out for free using Party Clusters © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19 High-Performance Computing (HPC)Azure provides high performance computing in the form of high performance virtual machines. These virtual machines are tailored to support this specific computing need, via features such as a backend network with MPI latency under three microseconds and up to 32 Gbps of throughput.

20 High-Performance Computing (HPC) Decisions12/20/2017 High-Performance Computing (HPC) Decisions Determine a strategy for on-premises, cloud, and hybrid clustering for HPC workloads Mandatory Scale the application resources dynamically, to take advantage of extreme size virtual machines only when it makes sense Recommended Make changes to the applications to allow disconnecting the tiers to take advantage of features, such as queuing to allow scaling of independent compute clusters Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21 Web & Mobile

22 Azure App Service Previously another type of PaaS application were Azure Websites. These have now been integrated into a new model that is called Azure App Services. App Services are comprised of the following subcomponents: Web Apps Mobile Apps API Apps Logic Apps

23 Azure App Service Model12/20/2017 Azure App Service Model New service definition for previously known Azure Websites. The websites model is based around the further decoupling from the underlying infrastructure of the traditional PaaS applications. This model removes the customer from any connection with the underlying VM that is hosting the application. No RDP. Hence, installation of components and software is only done through the Azure Portal (MarketPlace), which essentially packages the software to deploy to the website. Websites allow for the following scenarios and deployment model Provide a platform to host web applications and web services. Run backend type processes via a service offering in WebJobs. 1. Manual: file copy, ftp, and Web Matrix 2. Local Git: via Kudo environment 3. Continuous Integration: Git or TFVC © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24 Azure App Service Model12/20/2017 Azure App Service Model App services is one of the latest models to be employed on Azure. Focused on the idea to simplify the management and cost of running a variety of services in PaaS. A service performance level can be set at the app service level and then the various services can be deployed inside this app service. Hence, a web app could be deployed that is using an API app or Logic app and the cost and performance levels are set at the app service level. A model that simplifies the deployment because each app doesn’t need to be configured and billed separately. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25 Azure App Service Decisions12/20/2017 Azure App Service Decisions Understand that these lighter PaaS services do not allow direct access to the underlying virtual machines. No installation of components on the underlying web server (outside of the application folder). Mandatory Match the service offering with the type of workload. API apps differ from Web apps as one needs more focus on backend, while the other one on the front end. Recommended Plan for capacity needs. Although some thought should be given to how many instances or sizes should be used, these can easily be changed later. The focus here is on rapid deployment. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26 Mobile Engagement Azure Mobile Engagement is a software-as-a-service (SaaS) user-engagement platform that provides data-driven insights into app usage, real-time user segmentation, and enables contextually-aware push notifications and in-app messaging. It enables you to create and manage a targeted engagement strategy for your mobile applications. Contextually-aware push notifications and in-app messaging Real-time user segmentation Once you have collected app users' behavioral analytics data, we allow you to segment your audience based on various parameters and collected data to enable you to run targeted push campaigns. This is the core focus of the product - perform targeted and personalized push notifications. And for this to happen, we collect rich behavioral analytics data. Data-driven insights into app usage Software-as-a-service (SaaS): We provide cross platform SDKs to collect the behavioral analytics about the app users. Note the term behavioral analytics (as against performance analytics) because we focus on how the app users are using the app. We do collect basic performance analytics data about errors, crashes etc but that is not the core focus of the product. We have a portal separate from the Azure management portal which is optimized to interact and view rich behavioral analytics about the app users and run marketing push campaigns. The product is geared to get you going in no time!

27 Mobile Engagement Decisions12/20/2017 Mobile Engagement Decisions Start with a well-designed engagement plan to help you identify the granular data you will need to be able to segment your user base Mandatory Use an iterative, step-by-step approach to defining your engagement plan. Recommended Use the BET (Business, Engagement, Technical) model to define your key performance indicators Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

28 12/20/2017 API Management Models Use Azure’s API Management to centralize all framework for your company’s deployed web services. The developer is tasked with concentrating on business logic instead rather than “infrastructure” type code. Centralize your frameworks in Azure’s API management service to allow the underlying web services to be deployed on different servers and even different technologies. Ultimately, consolidating services from multiple back-ends to a single entry point for service consumers. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29 API Management Decisions12/20/2017 API Management Decisions Configure policies for services and profiles for existing web services to use API management. Mandatory Protect web services with API rate limits and quota policies. Recommended Customize the developer portal to allow for developer registration and subscription models. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30 Logic Apps Azure App Service is a fully managed PaaS (Platform as a Service) for developers that makes it easier to build web, mobile, and integration apps. Logic Apps are a part of this suite and allow any technical user or developer to automate business process execution and workflow using an easy-to-use visual designer. Best of all, Logic Apps can be combined with built-in Managed APIs to help solve tricky integration scenarios with ease. Easy to use design tools - Logic Apps can be designed end-to-end in the browser. Start with a trigger - from a simple schedule to whenever a tweet appears about your company. Then orchestrate any number of actions using the rich gallery of connectors. Get started quickly from templates - To help you get started we've provided a gallery of templates that allow you to rapidly create some common solutions. From advanced BizTalk solutions to simple SaaS connectivity, and even a few that are just 'for fun' - the gallery is the fastest way to understand the power of Logic Apps. Extensibility baked-in - Don't see the API you need? Logic Apps is designed to work with API apps; you can easily create your own API app to use as a custom API. Build a new app just for you, or share and monetize in the marketplace. Compose SaaS easily - Even composition tasks that are easy to describe are difficult to implement in code. Logic Apps make it a cinch to connect disparate systems. Want to create a task in your CRM software that is based on the activity from your Facebook or Twitter accounts? Want to connect your cloud marketing solution to your on-premises billing system? Logic apps are the fastest, most reliable way to deliver solutions to these problems. Real integration horsepower - Start easy and grow as you need. Logic Apps can easily leverage the power of BizTalk, Microsoft's industry leading integration solution to enable integration professionals to build the solutions they need. Find out more about the BizTalk capabilities provided with Logic Apps.

31 Logic Apps Decisions Mandatory Recommended Optional12/20/2017 Logic Apps Decisions Create conditional logic (a trigger) and an associated action (e.g. me) Mandatory Add conditional logic to your logic app (e.g. me after I’m followed 10 times on twitter). Recommended Use the code view to edit your logic app Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

32 Notification Hubs At a high level, all platform notification systems follow the same pattern: The client app contacts the PNS to retrieve its handle. The handle type depends on the system. For WNS, it is a URI or "notification channel." For APNS, it is a token. The client app stores this handle in the app back-end for later usage. For WNS, the back-end is typically a cloud service. For Apple, the system is called a provider. To send a push notification, the app back-end contacts the PNS using the handle to target a specific client app instance. The PNS forwards the notification to the device specified by the handle.

33 Notification Hubs Decisions12/20/2017 Notification Hubs Decisions Separate production and development environments into different hubs. The free tier lends itself to development purposes. If you require the ability to export telemetry/registration information or have multi-tenancy, use the standard tier. Mandatory For sending sensitive information, follow a secure push pattern, where a notification, with a message identifier but without sensitive data, is sent to the device and the device retrieves the sensitive data. Recommended Use tags to target specific registrations (i.e. devices, users, etc.) Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

34 Data

35 Azure SQL Database Fully managed SQL database serviceBuilt for SaaS and Enterprise applications Predictable performance & Pricing Elastic database pool for unpredictable SaaS workloads 99.99% availability built-in Geo-replication and restore services for data protection Secure and compliant for your sensitive data Fully compatible with SQL Server 2014 databases

36 Database Performance and ThroughputCompute DTU database throughput unit Writes Reads Memory

37 Predictable PerformanceBuild 2015 12/20/2017 5:58 AM Predictable Performance Basic, Standard, and Premium provide increasing performance levels Scale individual databases up/down via portal, PS, APIs, or T-SQL to reflect actual or anticipated demand Database remains online while scaling Hourly billing provides cost efficiency 5 10 20 50 100 250 1000 DTUs B S0 S1 S2 S3 P2 P3 P1 125 © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

38 Database Service TiersBasic Standard Premium Light transactional workloads Go-to option for most business applications High throughput and business-critical databases Intended Use 99.99%* Availability • •• ••• Performance Fully compatible with SQL Server 2014 databases Programming Surface Isolated databases and elastic database pools Workload Elasticity

39 Restore to point of deletionData Protection Regional Disaster Protection Geo-Restore Geo-Redundant Backups RPO < 1 hour Recovery Time Minutes to Hours Geo-Replication Asynchronous Replication RPO < 5 seconds < 30 seconds Recovery Point in time restore Continuous backup Restore to any-point Recovery Time Minutes to Hours Accidental Database deletion Tail-end backup Restore to point of deletion Recovery Time Minutes to Hours

40 Azure SQL Database Considerations12/20/2017 Azure SQL Database Considerations Features Performance Security Data can be encrypted by the application and stored in an Azure SQL database. However, TDE is not supported by Azure SQL. Consider SQL on IaaS for TDE scenarios. Azure SQL has a public facing IP accessible by anyone. Secure the connection to Azure SQL using a SQL Server firewall and SQL Database firewall. When using ExpressRoute and public peering, the NAT address interface on the Azure end has to be specified in the Azure SQL firewall rules. Azure SQL performance can appear to be slower, as each write will be committed to three databases in the local datacenter (synchronously) and another write (asynchronously) if geo replication enabled. This affords the benefit of not having to maintain local backups. Consider adding a caching layer for TPS loads. Advances features such as disk level or OS level access does not work with Azure SQL. Azure SQL does not allow CLR integration, backup sets, and FILESTREAM tables. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

41 Azure SQL Database Considerations12/20/2017 Azure SQL Database Considerations Plan models as follows: FILESTREAM Store the file object to Azure blob storage and store indexes in SQL FILESTREAM is not available wit Azure SQL databases SQL Backups Use geo-replication and point in time backups for Azure SQL workloads Traditional Backup sets are not supported in Azure SQL databases © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

42 Azure SQL Database Decisions12/20/2017 Azure SQL Database Decisions Understand the performance and management differences between traditional SQL database and Azure SQL database. Decide which option suits your needs the best. Mandatory Analyze databases to be migrated to Azure SQL database for incompatibles that might be present (E.G. FILESTREAM). Recommended Leverage built in tooling for BACPAC and DACPAC to move databases to Azure SQL databases. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

43 DocumentDB DocumentDB is a true schema-free NoSQL document database service designed for modern mobile and web applications. DocumentDB delivers consistently fast reads and writes, schema flexibility, and the ability to easily scale a database up and down on demand. It does not assume or require any schema for the JSON documents it indexes. By default, it automatically indexes all the documents in the database and does not expect or require any schema or creation of secondary indices. DocumentDB enables complex ad hoc queries using a SQL language, supports well defined consistency levels, and offers JavaScript language integrated, multi-document transaction processing using the familiar programming model of stored procedures, triggers, and UDFs. As a JSON database, DocumentDB natively supports JSON documents enabling easy iteration of application schema. It embraces the ubiquity of JSON and JavaScript, eliminating mismatch between application defined objects and database schema. Deep integration of JavaScript also allows developers to execute application logic efficiently and directly - within the database engine in a database transaction.

44 DocumentDB All resources within DocumentDB are modeled and stored as JSON documents. Resources are managed as items, which are JSON documents containing metadata, and as feeds which are collections of items. Sets of items are contained within their respective feeds. The image to the right shows the relationships between the DocumentDB resources

45 DocumentDB Decisions Mandatory Recommended Optional12/20/2017 DocumentDB Decisions Resources within DocumentDB are stored as JSON documents, typical of a document-based NoSQL database. Make sure this type of NoSQL database best fits your application’s data requirements. Mandatory Understand the four different consistency levels of DocumentDB and how each would impact your application’s consistency, availability, and performance. Recommended Use data partitioning to scale-out DocumentDB. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

46 Redis Cache The Redis Cache offering is cache as a service for the Azure platform. In this service the Azure platform will manage the underlying infrastructure to host the caching servers. Low latency, high throughput key-value store Atomic operations on data types Transactions Publisher-Subscriber pattern LUA scripting Pipelining Client libraries in multiple languages Highly customizable replication support Persistence support Clustering

47 12/20/2017 Redis Cache Model From an application perspective, Redis Cache can be accessed via its clients which are available for most of the popular selections today (Java, Node, .NET, etc.). Redis goes beyond simple key/value store to a cache that can contain entire data structures such as collections, sets, etc. Use Redis to support non-blocking first synchronization and auto reconnections, and to support replication of the cache to increase uptime. At its simplest, Redis can be described as something between a traditional database and doing computations in memory. Redis exposes data structures that are accessed in memory via a set of commands. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

48 Scaling Azure Redis CacheBuild 2013 12/20/2017 Scaling Azure Redis Cache Scale Up– aka Vertical Scaling Increased Cache Size (Memory) Increased Bandwidth Single CPU Scale Out– aka Horizontal Scaling Increased Cache Size, Bandwidth, CPU Improved Availability Sharding available in Premium SKU © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

49 Redis Cache Decisions Mandatory Recommended Optional12/20/2017 Redis Cache Decisions Understand which tier of service will be required and implement the Redis client in the application. Mandatory Use the advanced structure caching options with Redis to simplify the application caching code. Recommended Setup policies for cache rejection, lifetime, etc. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

50 12/20/2017 Azure Search A search as a service solution allowing developers to incorporate great search experiences into applications without managing infrastructure or needing to become search experts. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

51 12/20/2017 Azure Search Model While Azure Search does not offer a crawler to index the application data sources, it does provide the infrastructure to intake the index and provides interfaces for the actual search functions. The service is very targeted at developers, and is not a service that is directly customer facing. At a high level, the following is the graphical representation of the steps needed to model the Azure Search Service. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

52 12/20/2017 Azure Search Model The Azure Search Service, at its core, is a web service that follows the model of a REST based interface for connected applications. The indexes are a schema that are expressed in JavaScript Object Notation (JSON) and contain the following attributes: Name, Type, Searchable, Suggestions, Sortable, Retrievable, Filterable, and Facetable. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

53 Azure Search Decisions12/20/2017 Azure Search Decisions Construct and update indexes for Azure Search consumption via backend services. PaaS based worker roles work well for these types of jobs. Mandatory Add additional attributes to the index to support advanced features such as auto suggestions. Recommended Build monitoring data integration to existing monitors to ensure storage or indexes don’t exceed the limits for the service. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

54 Analytics

55 Azure HDInsight Implementation of Hadoop as a service in AzureEnables customers with the ability to create Hadoop cluster services in seconds and minutes instead of hours and days Significantly reduces the cost of admission to this big data service. Provides storage in the form of HDFS and Azure blob storage to be leveraged by Hadoop Microsoft’s cloud Hadoop offering 100% open source Apache Hadoop Built on the latest releases across Hadoop (2.6) Up and running in minutes with no hardware to deploy Harness existing .NET and Java skills Utilize familiar BI tools for analysis including Microsoft Excel

56 HDInsight Hive Dramatic performance gains with Stinger/TezSQL-like queries on Hadoop data in HDInsight HDInsight provides easy-to-use graphical query interface for Hive HiveQL is a SQL-like language (subset of SQL) Hive structures include well-understood database concepts such as tables, rows, columns, partitions Compiled into MapReduce jobs that are executed on Hadoop Dramatic performance gains with Stinger/Tez Stinger is a Microsoft, Hortonworks and OSS driven initiative to bring interactive queries with Hive Brings query execution engine technology from Microsoft SQL Server to Hive Performance gains up to 100x Microsoft contribution to Apache code Hadoop 2.0 1400s 44.3s 35.1s Sample Query Hive 10 HDP 1.3 / Hive 11 HDP 2.0 32x Speedup 40X Speedup 100x Speedup 15s HDP 2.1

57 HDInsight HBase NoSQL database on data in HDInsightColumnar, NoSQL database Runs on top of the Azure Blob Stores in HDInsight Provides flexibility in that new columns can be added to column families at any time HMaster Coordination Name Node Region Server Region Server Region Server Region Server Job Tracker Data Node Data Node Data Node Data Node Task Tracker Task Tracker Task Tracker Task Tracker

58 HDInsight Storm Stream analytics for Near-Real Time ProcessingConsumes millions of real-time events from a scalable event broker (ie. Apache Kafka, Azure Event Hub) Performs time-sensitive computation Output to persistent stores, dashboards or devices Customizable with Java + .NET Deeply integrated to Visual Studio Event Queuing System Collection Presentation and action Event producers Transformation Long-term storage Event Hubs Storage adapters Stream processing Cloud gateways (web APIs) Field gateways Applications Search and query Data analytics (Excel) Web/thick client dashboards Live Dashboards Apache Storm on HDInsight Devices to take action Kafka / RabbitMQ / ActiveMQ Web and Social Devices Sensors Azure Stream Analytics HDFS Azure DBs Azure storage HBase © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

59 Azure HDInsight running LinuxChoice of Windows or Linux clusters Managed & supported by Microsoft Re-use common tools, documentation, samples from Hadoop/Linux ecosystem Add Hadoop projects that were authored on Linux to HDInsight Easier transition from on-premises to cloud

60 Hadoop Visual Studio IntegrationDebug Hive jobs through Yarn logs or troubleshoot Storm topologies Visualize Hadoop clusters, tables, and storage Submit Hive queries, Storm topologies (C# or Java spouts/bolts) IntelliSense for authoring Hive jobs and Storm business logic

61 Azure HDInsight (Hadoop) Models12/20/2017 Azure HDInsight (Hadoop) Models Run HDInsight either on Linux or Windows based servers. HortonWorks Data Platform (HDP) is the Hadoop distribution used. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

62 Azure HDInsight (Hadoop) Models12/20/2017 Azure HDInsight (Hadoop) Models Additionally, there are several high level configurations for running Hadoop which can be used to optimize the cluster based on the operations and activities it will target. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

63 Azure HDInsight (Hadoop) Decisions12/20/2017 Azure HDInsight (Hadoop) Decisions Create storage accounts for data repositories for HDInsight. Also, Deprovision your clusters when not in use, as the costs for running thousands of cores can quickly add up. Mandatory Get a good sense for your data and what is most important to your workloads. This will help guide what components in HDInsights can be leveraged to take the best advantage of the platform services. Recommended Spend more time checking out what has already been built by the open source communities that can be used with much less effort than writing from scratch. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

64 Data Lake Store Azure Data Lake Store is an enterprise-wide hyper-scale repository for big data analytic workloads. Azure Data Lake enables you to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics.

65 Data Lake Store Decisions12/20/2017 Data Lake Store Decisions Use appropriate mechanisms to secure access to Azure Data Lake Storage via Azure AD authentication, ARM RBAC feature and/ POSIX-style permissions exposed by the WebHDFS protocol. Mandatory When using the Import/Export service, the file sizes on the disks that you ship to Azure data center should not be greater than 200 GB. Recommended Integrate Azure Data Lake Store with other services – i.e. provision an Azure HDInsight cluster that uses Data Lake Store as the HDFS-compliant storage, use Azure Data Lake Storage as a Azure Data Factory data source or access it from OSS applications, such as Apache Sqoop, Apache Storm or Apache Hive. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

66 Data Lake Analytics Azure Data Lake Analytics is a new service, built to make big data analytics easy. This service lets you focus on writing, running and managing jobs, rather than operating distributed infrastructure. Instead of deploying, configuring and tuning hardware, you write queries to transform your data and extract valuable insights. The analytics service can handle jobs of any scale instantly by simply setting the dial for how much power you need. You only pay for your job when it is running making it cost-effective.

67 Data Lake Analytics Decisions12/20/2017 Data Lake Analytics Decisions None Mandatory Use Azure Data Lake Analytics as a preferred option to derive insights from massive amounts of data. Recommended Integrate Azure Data Lake Analytics with other services – use Azure Blob storage, Azure SQL database, and Data Lake Analytics as a data source for Azure Data Lake Analytics queries. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

68 Azure Machine LearningPowerful cloud-based predictive analytics service that makes it possible to quickly create and deploy predictive models as analytics solutions Provides tools to model predictive analytics Provides a fully-managed service to publish your predictive models as ready-to-consume web services

69 Azure Machine Learning Model12/20/2017 Azure Machine Learning Model Toolset to create Azure ML experiments include the Azure Machine Learning Studio An experiment consists of dragging components to a canvas, and connecting them in order to create a model, train the model, and score and test the model. The experiment uses predictive modeling techniques in the form of Machine Learning Studio modules that ingest data, train a model against it, and apply the model to new data. You can also add modules to preprocess data and select features, split data into training and test sets, and evaluate or cross-validate the quality of your model. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

70 Azure Machine Learning Decisions12/20/2017 Azure Machine Learning Decisions Bring your R and Python code libraries and understand how to leverage ML Studio to provide streamlined development experience. Mandatory Partition your logic to create consumable services by using the platform services of ML. Recommended Explore what the data science community has already created and look to extend or enhance these solutions instead of creating them from scratch to speed the development effort time. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

71 Azure Data Factory Azure Data Factory is a cloud-based data integration service that orchestrates and automates the movement and transformation of data. It orchestrates existing services that collect raw data and transform it into ready-to-use information. ADF is used to collect data from many different on-premises data sources, ingest and prepare it, organize and analyze it with a range of transformations, then publish ready-to-use data for consumption. Beyond orchestrating the flow of a data pipeline, ADF offers a single unified view to easily pinpoint issues and setup monitoring alerts.

72 Azure Data Factory Decisions12/20/2017 Azure Data Factory Decisions Configure a dataset, activity, linked service and pipeline Mandatory Set up monitoring alerts to be notified when extraneous events occur Recommended Use a data management gateway (if you’re using ADF to access data on premises) Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

73 Stream Analytics Stream Analytics is a real time stream processing service used to uncover insights from devices, sensors, infrastructure, and applications. Streaming millions of events per second, stream analytics can be used to perform real-time analytics for IoT solutions. Developers can describe their desired event stream processing and transformations using a SQL-like query language. The system abstracts the complexities of the parallelization, distributed computing, and error handling.

74 Stream Analytics Decisions12/20/2017 Stream Analytics Decisions Configure a data stream input and an output. Mandatory Create a SQL-like query to process data on the fly. Configure data ingestion service (e.g. event hub) and stream analytics in multiple environments to prevent any downtime of application. Recommended Use a reference data input as a lookup. Use Stream Analytics to feed data directly into PowerBI to create a dashboard view of your data. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

75 Internet of Things (IoT)

76 IoT Hub Azure IoT Hub is a fully managed service that enables reliable and secure bidirectional communications between millions of IoT devices and a solution back end. Azure IoT Hub: Provides reliable device-to-cloud and cloud-to-device messaging at scale. Enables secure communications using per-device security credentials and access control. Provides extensive monitoring for device connectivity and device identity management events. Includes device libraries for the most popular languages and platforms.

77 IoT Hub Decisions Mandatory Recommended Optional12/20/2017 IoT Hub Decisions Anticipate the number of messages you expect to receive per day. The current message limit is 6 million messages/unit/day. The maximum unit count for S2 IoT Hub is 200. If more units more required, you must contact Microsoft Support. Mandatory If protocol translation is necessary, utilize the Azure Protocol Gateway as a starting point for your solution. The currently supported protocols are AMQP and MQTT Recommended Understand the differences between IoT Hub and Event Hub to identify which service works best for your solution. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

78 Event Hubs Azure Event Hub is an event processing service that provides event and telemetry ingress to the cloud at massive scale, with low latency and high reliability. This service, used with other downstream services, is particularly useful in application instrumentation, user experience or workflow processing, and Internet of Things (IoT) scenarios. Event Hub provides a message stream handling capability and, though an Event Hub is an entity similar to queues and topics, it has characteristics that are very different from traditional enterprise messaging. Enterprise messaging scenarios commonly require a number of sophisticated capabilities such as sequencing, dead-lettering, transaction support, and strong delivery assurances, while the dominant concern for event intake is high throughput and processing flexibility for event streams. Therefore, Azure Event Hub capabilities differ from Service Bus topics in that they are strongly biased towards high throughput and event processing scenarios.

79 Event Hubs Decisions Mandatory Recommended Optional12/20/2017 Event Hubs Decisions Event Hubs Standard tier currently supports a maximum retention period of 7 days. Note that Event Hubs are not intended as a permanent data store. Mandatory Do not grant tokens with direct access that will be used by devices. This prevents blacklisting and throttling. Recommended Consider long term scale needs prior to creating the Event Hub as the partition count cannot be changed. The number of partitions must be between 2 and 32. You can increase the 32 partition limit by contacting support. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

80 Media & CDN

81 Media Services Microsoft Azure Media Services is an extensible cloud-based platform that enables developers to build scalable media management and delivery applications. Media Services is based on REST APIs that enable you to securely upload, store, encode and package video or audio content for both on-demand and live streaming delivery to various clients (for example, TV, PC, and mobile devices). You can build end-to-end workflows using entirely Media Services. You can also choose to use third-party components for some parts of your workflow. For example, encode using a third-party encoder. Then, upload, protect, package, deliver using Media Services. You can choose to stream your content live or deliver content on demand.

82 Media Service Decisions12/20/2017 Media Service Decisions After you regenerate a storage key, you must make sure to synchronize the update with Media Services. Mandatory If you are just looking to store JPEG or PNG images, you should keep those in Azure Blob Storage. There is no benefit to putting them in your Media Services account unless you want to keep them associated with your Video or Audio Assets. Recommended Currently, the max recommended duration of a live event is 8 hours. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

83 Content Delivery NetworkCDN networks are used for static content such as media, images or documents which are read more than written to. The end goal being to push content to areas of the world where users are located. Speed Reliability Efficiency In almost every case, content utilizing a CDN will be much closer to the end-user and that will result in faster delivery and a better user experience The CDN spreads out content, replicating that content across the globe, resulting in reduced demand on any given server The CDN optimizes for delivery, allowing the customer to focus on the quality of their content, not on the delivery of that content

84 Core CDN Traffic Flow and ValuesMicrosoft Ignite 2015 12/20/2017 5:58 AM Core CDN Traffic Flow and Values Customer Origin Server CDN Edge Network HTTP Client First Request Subsequent Requests © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

85 Content Delivery Network Model12/20/2017 Content Delivery Network Model Azure’s CDN is a network of severs deployed in multiple data centers across the Internet that can get your content from where you are to where your customer are consuming more quickly than the Internet alone. Typically CDN networks are used for static content such as media, images, or documents which are read more than written to. The following are examples: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

86 Content Delivery Network Decisions12/20/2017 Content Delivery Network Decisions Determine regions to target for CDN and update application to use root URI of CDN network as opposed to local content. Mandatory Leverage parameters to vary the caching characteristics and lifetime of content cache. Recommended Map the CDN content to a custom domain name. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

87 Hybrid Integration

88 Hybrid Connections Hybrid Connections are a feature of Azure BizTalk Services. Hybrid Connections provide an easy and convenient way to connect the Web Apps feature in Azure App Service (formerly Websites) and the Mobile Apps feature in Azure App Service (formerly Mobile Services) to on-premises resources behind your firewall. Hybrid Connections support the following framework and application combinations: .NET framework access to SQL Server .NET framework access to HTTP/HTTPS services w/ WebClient PHP access to SQL Server, MySQL Java access to SQL Server, MySQL and Oracle Java access to HTTP/HTTPS services

89 Hybrid Connections Decisions12/20/2017 Hybrid Connections Decisions TCP-based services that use dynamic ports (such as FTP Passive Mode or Extended Passive Mode) are currently not supported. Mandatory You can scale Hybrid Connections by installing another instance of the Hybrid Connection Manager on another server. Configure the on-premises listener to use the same address as the first on-premises listener. In this situation, the traffic is randomly distributed (round robin) between the active on-premises listeners. Recommended Use Group Policy to control the on-premises resources used by a Hybrid Connection. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

90 12/20/2017 Azure Service Bus Service bus is a high performance, durable messaging service for queueing, as well as, relay services. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

91 12/20/2017 Azure Service Bus Service Bus queues are used to provide an option to decouple any processing from the request pipelines. Consider these types of architectures, especially when migrating workloads to the cloud as loosely coupled applications can scale and are more fault resilient than the counter. Use service bus with a variety of models from simple queues based storage, to topics, which target and partition messages in a namespace. Consider using Event Hubs on top of Service Bus to service very large client bases, where inputs to the bus will include several thousands to millions in rapid succession. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

92 Azure Service Bus Models12/20/2017 Azure Service Bus Models Enable multiple concurrent consumers to process messages received on the same messaging channel. This pattern enables a system to process multiple messages concurrently to optimize throughput, improve scalability and availability, and to balance the workload. Competing Consumer Patterns: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

93 Azure Service Bus Models12/20/2017 Azure Service Bus Models Priority Queue Pattern: Prioritize requests sent to services so that requests with a higher priority are received and processed more quickly than those of a lower priority. This pattern is useful in applications that offer different service level guarantees to individual types of clients. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

94 Azure Service Bus Models12/20/2017 Azure Service Bus Models Use a queue that acts as a buffer between a task and a service that invokes in order to smooth the intermittent heavy loads that may otherwise cause the service to fail or the task to timeout. This pattern can help to minimize the impact of peaks in demand and availability and responsiveness for both the task and the service. Queue-based Load Leveling Pattern: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

95 Azure Service Bus Models12/20/2017 Azure Service Bus Models Coordinate a set of actions across a distributed set of services and other remote resources, attempt to transparently handle faults if any of these actions fail, or undo the effects of the work performed if the system cannot recover from a fault. This pattern can add resiliency to a distributed system by enabling it to recover and retry actions that fail due to transient exceptions, long-lasting faults, and process failures. Scheduler Agent Supervisor Pattern: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

96 Azure Service Bus Models12/20/2017 Azure Service Bus Models Decompose a task that performs complex processing into a series of discrete elements that can be reused. This pattern can improve performance, scalability, and reusability by allowing task elements that perform the processing to be deployed and scaled independently. Pipes and Filters Pattern: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

97 Azure Service Bus Models12/20/2017 Azure Service Bus Models Use queues and topics to separate endpoints and devices from clients to enable temporary separation for occasionally connected devices and services. This pattern improves scale and durability while providing separation and security on a per device basis. Command and Control Pattern: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

98 Azure Service Bus Models12/20/2017 Azure Service Bus Models Distribute messages over multiple channels to one or more recipients in parallel. This pattern improves scale and reduces latency by spreading messages to one or more downstream. Unlike load leveling this pattern partitions data across subscriptions on topics. This can be accomplished with ForwardTo or Subscriptions features. Fan Out Pattern: © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

99 Service Bus Decisions Mandatory Recommended Optional12/20/2017 Service Bus Decisions Determine which model to use when storing messages in Service Bus, based on transaction, lifetimes, and message rates. Mandatory Modify applications to provide transient fault handling to compliment the decoupling of message posting from message processing. Recommended Leverage Event Hubs in addition to Service Bus to handle large scale intake of service bus messages. Optional © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

100 12/20/2017 5:58 AM Key Decisions © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

101 Deployment Methods Decisions12/20/2017 Deployment Methods Decisions Models for application lifecycle vary from simple to complex. Some of the most important tradeoffs are outlined below: Considerations Decision Points Upgrade Domains - Configure PaaS Web and Worker Roles services to use multiple upgrade domains to avoid unnecessary outages when new deployment upgrades to the application or services are initiated. Deployment Slots Use deployment slots to “test” new version or upgrades without affecting the production application. Choose to stage slots before releasing to production, which can enable better testing to avoid downtime. Web Deploy Choose that larger apps require more governance and control around the deployment. Continuous Integration - Choose continuous integration for larger applications and organizations that require the automation of deployments. This allows for both gated check-ins (approval) and continuous (triggered). © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

102 Load Balancing Decisions12/20/2017 Load Balancing Decisions When deploying Azure PaaS application consider load balancing as a core part of the application. There exist two levels of load balancing for Azure PaaS services: Considerations Decision Points DNS Level Choose this option when needing to load balance traffic to different cloud services located in different datacenters, to different Azure websites located in different datacenters, or to external endpoints. Choose Traffic Manager and the Round Robin load balancing method. Network Level Choose this option when needing to load balance incoming internet traffic to different VMs of a cloud service. Implement this solution with Azure Load Balancer. Choose between the different options of Internal and External load balancers. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

103 12/20/2017 Networking Decisions When deciding to provision PaaS instances that will need to communicate with other servers or services in Azure a Virtual Network will be required. The following are areas to consider: Considerations Decision Points Name Resolution Choose to deploy a DNS solution for VMs and cloud service in a Vnet. Decide between the Azure provided name resolution or your own DNS solution depending on the name resolution requirements. Enhances Security and Isolation Use the Vnet as an added layer of isolation to the services, such as VMs and cloud services deployed within the Vnet. Extended Connectivity Boundary Use a Vnet to extend the connectivity boundary from a single service to the Vnet boundary. Consider setting up services that use a common backend database tier or use a share management service, in a Vnet. Extend your on-premises network to the cloud Join VMs in Azure to the on-premises domain in order to access and leverage all on-premises investments around monitoring and identity for the services hosted in Azure. Use persistent public IP addresses Consider configuring your cloud services with a reserved public IP address from the address range when you create it. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

104 12/20/2017 Networking Decisions Decide on which model to leverage for the networking configuration in Azure for your cloud services. Considerations Decision Points Cloud-Only In this model, no Vnet gateways are deployed and connection to the VMs and cloud services is done though the endpoints rather than through a VPN connection. Cross-Premises In this model, you can create multi-site configurations, Vnet to Vnet configurations, ExpressRoute connections allowing you to leverage on premises connectivity and resources. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

105 Limitations Decisions12/20/2017 Limitations Decisions Consider the limitations which exist: Considerations Decision Points Auto-Scaling Consider utilizing monitoring and automation capabilities such as the Azure Monitoring Agent and Azure Automation to dynamically scale and deploy application code to cloud service instances. Load Balancing Consider creating and internal load balancer to the cloud services provisioned and associate them with the cloud service endpoint. Density Leverage multiple subscriptions to provide the proper level of segmentation and avoid hitting limits (e.g. total cloud services per subscription is 20) © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

106 Azure PaaS Cloud Services Management Decisions12/20/2017 Azure PaaS Cloud Services Management Decisions Consider the following diagnostic and monitoring Azure tools: Considerations Decision Points IIS Logs - Consider gathering information about IIS web sites Azure Diagnostic Infrastructure Logs - Consider gathering information about diagnostics itself IIS Failed Request Logs - Consider gathering information about failed requests to an IIS site or application Windows Event Logs - Consider gathering information sent to the Windows Event Logging System Performance Counters - Consider gathering OS and custom performance counters Crash Dumps - Consider gathering information about the state of the process in the event of an application crash Custom Error Logs - Consider gathering logs created by your application or service .NET EventSource - Consider gathering events generated by your code using .NET EventSource class Manifest Based ETW - Consider gathering ETW events generated by any process © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

107 12/20/2017 5:58 AM © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.