MicroSoft Azure 介绍

五个流行的云计算平台推荐最近几年，云计算成为了炙手可热的领域，许多企业和个人都将自己的数据和应用迁移到了云上，以享受云计算平台带来的便利和效益。

然而，在众多的云计算平台中，哪些是最受欢迎和推荐的呢？下面将介绍五个流行的云计算平台。

首先，AWS（亚马逊云计算服务）可以说是云计算平台中的巨头。

AWS提供了广泛的云服务，包括计算、存储、数据库、网络和人工智能等方面。

AWS的优势在于其庞大的全球基础设施，可以满足大规模的计算和存储需求。

此外，AWS还提供了简单易用的界面和丰富的开发工具，使用户能够轻松地部署和管理自己的应用。

其次，Microsoft Azure是另一个备受推崇的云计算平台。

作为微软的云服务，Azure凭借其强大的整合性和兼容性受到了广泛的认可。

Azure提供了一系列的云服务，包括虚拟机、存储、容器和人工智能等。

与此同时，Azure还与微软的其他产品和服务紧密结合，使用户能够无缝地将自己的应用迁移到云上。

Google Cloud Platform（谷歌云平台）是云计算领域的另一颗明星。

作为谷歌旗下的云服务，Google Cloud Platform凭借其强大的技术实力和创新能力脱颖而出。

该平台提供了丰富的云服务，包括计算、存储、数据库和机器学习等方面。

与此同时，Google Cloud Platform还具有良好的可扩展性和灵活性，可以满足各种规模和需求的用户。

接下来是阿里云，作为中国最大的云计算服务提供商之一，阿里云在国内市场具有巨大的影响力。

阿里云提供了全面的云计算服务，包括计算、存储、数据库和安全等方面。

此外，阿里云还与阿里巴巴集团的其他业务相互融合，为用户提供了全方位的解决方案。

阿里云还具有良好的性能和稳定性，可以满足用户对高可用性和安全性的需求。

最后，IBM Cloud是云计算领域的重要参与者之一。

作为国际知名的科技巨头，IBM Cloud凭借其在企业级市场的优势得到了广泛的好评。

mah证书分类-回复mah证书分类是指Microsoft Azure技术领域的一系列认证证书。

微软Azure是一家全球领先的云计算平台，为企业提供各种云服务。

拥有mah 证书可以证明持有人在Azure技术方面具备专业知识和技能，增加求职者的竞争力，同时也为企业提供了理想的人才选择。

在微软Azure领域，mah证书按照不同的专业能力和技术方向进行分类。

以下将逐步介绍现有的mah证书分类及其相关知识和要求。

1. AZ-900 Azure基础证书：AZ-900证书是一项基础认证，适用于所有希望了解Azure云技术、功能和解决方案的人员。

它主要涵盖了Azure云服务的基础知识，包括云概念、Azure服务、Azure解决方案的优势和应用场景等。

获得这个证书可以证明你理解Azure基本概念并能够进行初步的云计算工作。

2. AZ-103和AZ-104 Azure管理员证书：AZ-103证书（后续将更名为AZ-104）是一项面向Azure管理员的考试和证书。

它要求候选人具备基础的Azure云知识和技能，包括Azure 安全性、网络、存储、虚拟机管理以及资源监控与优化等方面的内容。

获得AZ-103（或AZ-104）证书将证明你在Azure管理方面具备实际经验和技能，可以负责设置和维护Azure环境。

3. AZ-203和AZ-204 Azure开发者证书：AZ-203证书（后续将更名为AZ-204）是一项针对Azure开发者的证书。

它要求候选人掌握基于Azure的应用程序开发技术和工具，包括使用Azure SDK、Azure存储、Azure认知服务、Azure函数等来构建和部署云应用程序。

获得AZ-203（或AZ-204）证书将证明你具备在Azure开发方面的技能和能力，可以为企业构建和维护Azure应用程序。

4. AZ-300和AZ-301 Azure解决方案架构师证书：AZ-300和AZ-301证书是一套与Azure解决方案架构师相关的证书。

世界三大云计算巨头云计算是当今科技领域中最重要的发展趋势之一。

它提供了一个强大的计算和数据存储解决方案，不仅可以满足企业和个人用户的需求，还为创新和发展提供了更多的机会。

在全球范围内，有三家公司被公认为世界三大云计算巨头，它们分别是亚马逊、微软和谷歌。

亚马逊是云计算领域的领军公司，其云计算服务AWS（Amazon Web Services）在市场上占据了主导地位。

AWS提供了一系列强大的云计算服务，包括计算、存储、数据库、机器学习和人工智能等。

通过AWS，用户可以根据自身需求弹性地扩展和管理其计算和存储资源。

此外，AWS还提供了全球范围内的数据中心，确保用户的业务能够以高可靠性和高性能运行。

微软是另一家在云计算领域中具有重要地位的公司。

其云计算平台Azure是全球最大的云服务提供商之一。

Azure提供了广泛的云计算服务，包括基础设施即服务（IaaS）、平台即服务（PaaS）和软件即服务（SaaS）。

Azure的优势在于其与微软的其他产品和服务的紧密集成，如Office 365和Dynamics 365。

通过Azure，用户可以轻松地构建、部署和管理应用程序和服务。

谷歌是第三家被列入世界三大云计算巨头的公司。

谷歌云平台（Google Cloud Platform）为企业和开发者提供了全面的云计算解决方案。

谷歌云提供了一系列的计算、存储、数据库和人工智能服务，如虚拟机、云存储、BigQuery和TensorFlow等。

谷歌云以其强大的技术实力和可靠性而闻名，许多知名企业和初创公司都选择了谷歌云作为其核心的云计算平台。

这三家公司作为世界三大云计算巨头，它们在技术、规模和全球覆盖范围方面都具有竞争优势。

亚马逊的AWS以其先进的基础设施和丰富的服务获得了广泛的用户认可。

微软的Azure凭借其与其他微软产品和服务的集成，为用户提供了一体化的解决方案。

谷歌云则以其出色的技术和可靠性吸引了众多用户。

在未来，云计算将会继续发展壮大，这三家云计算巨头将面临更多的竞争和机遇。

Microsoft Azure Multi-Factor Authentication- Adoption KitVersion: 3.0For the latest version, please check https://aka.ms/aadadoptionkitsContentsMicrosoft Azure Multi-Factor Authentication- Adoption Kit (1)Awareness (2)Business overview (2)Key benefits (3)Pricing and licensing requirements (3)Announcements/blogs (3)Training/learning resources (4)Level 100 concepts (4)Training resources (4)Videos (4)Books (5)Online courses (5)Whitepaper (5)Plan and change management (6)Deployment plan (6)Quickstarts (6)End-user readiness and communication (6)Combined registration with Self-Service Password Reset (7)Customer stories/case studies (8)Support and feedback (8)Next steps (8)AwarenessThis section helps you to analyze the benefits of Microsoft Azure Multi-Factor Authentication. You will learn about the ease of use, benefits, pricing, and licensing model. You can also access up-to-date announcements and blogs that discuss ongoing improvements.Business overviewThe following adoption kit is specific to Microsoft Azure Multi-Factor Authentication and does not cover the Multi-Factor Authentication server. For information on the Multi-Factor Authentication server, see Getting started with Multi-Factor Authentication Server.Multi-Factor Authentication helps safeguard access to data and applications while meeting user demand for a simple sign-on process. It delivers strong authentication via a range of easy verification options—phone call, text message, mobile app notification, or one-time passwords—allowing users to choose the method they prefer. It can be used both on-premises and in the cloud to add security for accessing Microsoft online services, Azure AD-connected SaaS applications, line of business applications, and remote access applications.for general, billing models, user experiences, andKey benefitsUsing Multi-Factor Authentication gives you the following benefits:Easy to set upYour applications or services do not need to make any changes to use Multi-FactorAuthentication. The verification prompts are part of the Azure AD sign-in event, whichautomatically requests and processes the Multi-Factor Authentication challenge whenrequired. It is designed for administrators to easily set up, use, and monitor.ScalableBasic Multi-Factor Authentication features are available at no extra cost. You canupgrade to scale for a greater number of users or groups. You can integrate with ActiveDirectory and on-prem applications as well as cloud-based applications.Always protectedTo enable protection for specific sign-in events, you can configure Conditional Accesspolicies. Coupling Conditional Access with Azure AD Identity Protection which detectsanomalies and suspicious events, allows you to require Multi-Factor Authenticationwhen sign-in risk is medium or high.ReliableMicrosoft guarantees 99.9% availability of Multi-Factor Authentication. This feature isespecially dependable for accounts with privileged access to resources.Intuitive user experienceUsers likely already use Multi-Factor Authentication with personal and other accounts,and their experience is that it is simple to activate and use. The extra protection thatcomes with Multi-Factor Authentication allows users to manage their own devices. Pricing and licensing requirementsinformation on pricing and billing, see Azure AD pricing.Announcements/blogsAzure AD receives improvements on an ongoing basis. To stay up to date with the most recent developments, refer to What's new in Azure AD?Training/learning resourcesThe following resources are a good start to learn about Multi-Factor Authentication. They include level 100 concepts, videos by our experts, books, link to online courses, and useful whitepapers for reference.Level 100 conceptsMicrosoft understands that some organizations have unique environment requirements or complexities. If yours is one of these organizations, use these recommendations as a starting point. However, most organizations can implement these recommendations as suggested.•Find what is the identity secure score in Azure AD?••Understand identity and device access configurations.Refer to the following links to get started with Multi-Factor Authentication:•Read the Azure Multi-Factor Authentication overview•Learn about authentication and verification methods available in Azure AD•Learn how Azure Multi-Factor Authentication works?•Understand Conditional Access policies and security defaults.•••••Frequently asked questions (FAQs) about Azure Multi-Factor AuthenticationFor more information, deep-dive into Authentication documentation.Training resourcesVideosHow to register your security information in Azure Active Directory Learn how to register the security information through Azure AD for security features like Multi-Factor Authentication and Self-Service Password Reset. End users will also learn how to view and manage their security methods in Azure AD.BooksSource: Microsoft Press - Modern Authentication with Azure Active Directory for Web Applications (Developer Reference) 1st Edition.Learn the essentials of authentication protocols and get started with Azure AD. Refer to examples of applications that use Azure AD for their authentication and authorization, including how they work in hybrid scenarios with Active Directory Federation Services (ADFS).Online coursesRefer to the following courses on Multi-Factor Authentication at :WhitepaperPlan and change managementIn this section, you deep-dive into planning and deploying Multi-Factor Authentication in your organization. Deployment planPlanning your Multi-Factor Authentication deployment is critical to make sure you achieve the required authentication strategy for your organization.QuickstartsFollow the step-by-step guidance to:•Set up Multi-Factor Authentication•Enable Security defaults•Secure user sign-in events with Azure Multi-Factor Authentication•Use risk detections for user sign-ins to trigger Azure Multi-Factor Authentication or password changes End-user readiness and communicationDownload Multi-Factor Authentication rollout materials and customize them with your organization's branding. You can distribute the readiness material to your users during Multi-Factor Authentication rollout, educate them about the feature, and remind them to register.Combined registration with Self-Service Password ResetWe recommend that you enable combined security information registration in Azure AD for SSPR and Multi-Factor Authentication.understand the functionality and effects of this feature. In case of issues, refer to Troubleshooting combined security information registration.Customer stories/case studies Discover how most organizations have come to understand the need for securing cloud identities with a second layer of authentication like Multi-Factor Authentication.The following featured stories demonstrate these needs:Wipro Limited – Wipro drives mobile productivity with Microsoft cloud securitytools to improve customer engagements. The IT team uses a combination of singlesign-on capabilities and Multi-Factor Authentication to support conditional access,including device-state conditional access.Orica – Explosives provider simplifies business and improves data access with SAPS/4HANA on Azure. Orica uses Azure services for additional protection, such asautomatically requiring anyone seeking access to the software and serviceapplications to verify their identity through Multi-Factor Authentication.Aramex delivery limited - Global logistics and transportation company createscloud-connected office with identity and access management solution . Ensuringsecure access was especially difficult with Aramex’s remote employees. The companyis now applying conditional access to let these remote employees access their SaaSapplications from outside the network. The conditional access rule will decidewhether to enforce Multi-Factor Authentication, giving only the right people theright access.Support and feedbackHow can we improve Multi-Factor Authentication? This section provides links to discussion forums and technical community support email IDs.We encourage you to join our Technical Community , a platform to Microsoft Azure AD users and Microsoft to interact. It is a central destination for education and thought leadership on best practices, product news, live events, and roadmap. If you have technical questions or need help with Azure, please try StackOverflow or visit the MSDN Azure AD forums. Tell us what you think of Azure and what you want to see in the future. If you have suggestions, please submit an idea or ontact a support professional through Multi-Factor Authentication Server (PhoneFactor) support .Next steps。

五大云计算平台比较分析在当今信息技术愈演愈烈的时代，云计算技术得到了快速普及和广泛应用。

随着市场竞争的加剧，各大云计算平台不断推陈出新地提高服务水平，为用户提供更加完善的云计算解决方案。

本文将分别分析AWS、Azure、Google Cloud、Alibaba Cloud、华为云这五大云计算平台的特点和优势。

一、AWS（亚马逊云计算）AWS是由亚马逊公司推出的一款云计算平台。

作为全球最大的云计算平台，AWS不断推陈出新，丰富其云计算、IaaS、PaaS、SaaS等服务实力。

AWS对于人工智能、大数据等领域有着丰富的技术积累和经验，可直接应用于企业级业务。

AWS的优点是：1.强大的安全性：AWS建立了全面的安全体系，可以避免大规模的攻击和数据泄露。

2.强大的扩展性：AWS具备优秀的扩展性，可以根据客户业务需求灵活满足客户的需求。

3.灵活的计费方式：AWS的计费方式非常灵活，可以根据用户的实际需求进行计费，大大降低了用户的使用成本。

二、Azure（微软云计算）Azure全称是“Microsoft Azure”，是微软公司推出的一款云计算平台。

作为全球大型IT企业，微软在云计算领域拥有丰富的经验和技术优势。

Azure在国内已经开设了多个数据中心，使用户能够更好地服务本地业务。

Azure的优点是：1.强大的生态支持：微软可以提供Azure、Office 365、Azure Active Directory等集成的生态系统支持，使得企业内部协作更加便捷。

2.高性能的网络架构：Azure具备卓越的网络架构性能，可以提供极佳的数据处理速度和集成能力。

3.价值最大化：Azure服务强调价值等比计价。

这意味着用户可以根据实际使用需求随时租用所需的计算能力以及网络服务。

三、Google Cloud（谷歌云计算）作为一个技术大国，Google在市场上的表现相对来说比较犹豫。

谷歌云计算（Google Cloud）是谷歌公司推出的云服务，不仅具有谷歌公司在技术和运维方面的优势，还具有丰富的应用场景，非常适合大型项目的高效开发。

Azure Assessment: Prerequisites andConfigurationThis document explains the required steps to configure the Azure Assessment included with your Microsoft Azure Log Analytics Workspace and entitled Microsoft On-Demand assessment.There are configuration and setup tasks to be completed prior to executing the assessment setup tasks in this document. For all pre-work, follow the Getting Started with On-Demand Assessments in the Services Hub Resource Center.Table of Contents2 Supported Environments (2)Environment Permissions (2)Data Collection Machine (2)Getting started with Microsoft Azure Assessment (3)Setup the Azure AD Application for Graph API authentication (3)Setup the Azure Assessment (5)Configure with User Account (5)Scheduled Task Details (7)Appendix (8)Data Collection Methods (8)Troubleshooting Azure Assessment Setup (8)General Troubleshooting OnDemand Assessment Guide (8)Azure datacenter IP address ranges (8)New-MicrosoftAssessmentApplication (8)Prerequisites Error (9)System Requirements and Configuration at GlanceAccording to the scenario you want to use, review the following details to ensure that you meet the necessary requirements.Supported Environments•Azure AD tenant (AzureCloud, AzureChinaCloud, AzureGermanCloud, AzureUSGovernment)Environment Permissions•Assessment account rights:o An assessment scheduled task account with the following rights:▪Administrative access to the data collection machine▪Log on as a batch job privileges on the data collection machineo An Azure AD account for the setup of the Azure AD Registered Application with the following properties ▪Global Administrator▪Non-Federatedo An Azure AD account for assessment execution (can be separate account than above)▪Global Reader▪Non-Federated▪MFA DisabledData Collection Machine• A data collection machine running the Azure Assessment requires computers running Windows Server 2016 or Windows Server 2019 or Windows 10.•The data collection machine may be Azure AD joined, Active Directory joined, or Workgroup joined.•The data collection machine must be able to connect to the Internet using HTTPS to successfully perform all steps detailed in this document. This connection can be direct, or via a proxy.•Data collection machine hardware: Minimum 8 gigabytes (GB) of RAM, 2 gigahertz (GHz dual-core processor, minimum 10 GB of free disk space.•Microsoft .NET Framework 4.6.2 or newer installedo Download from: https:///download/dotnet-framework-runtime/net462•The CLR version on the data collection machine should be using .NET 4.0 or greater. This can be verified by running $PSVersionTable.CLRVersion in the PowerShell prompt•Azure AD Preview Module for PowerShell needs to be installed (this will be installed automatically)•MSOnline Powershell module. Install MSOnline PowerShell module:1.Open a PowerShell session with Administrator privileges2.On Start Menu type: PowerShell3.Right Click on the Icon and choose Run as Administrator4.On the shell type the following command: Install-Module MSOnline -Verbose -AllowClobber -ForceGetting started with Microsoft Azure AssessmentBe sure to complete the steps in the following link before proceeding to assessment setup:https:///en-us/services-hub/health/getting-started-azureSetup the Azure AD Application for Graph API authentication.1.Open a PowerShell session on the data collection machine with Administrator privileges.2.Ensure the running of scripts is permitted on the machine: Set-ExecutionPolicy RemoteSigned.3.Run the following cmdlet: New-MicrosoftAssessmentsApplication.4.This will prompt for Azure AD tenant Global administrator credentials:5.Enter the credentials for the Azure AD Tenant Global Administrator to be used to create the Azureapplication.6.Once the credentials are entered the application will be created, the AzureAD Preview PowerShell moduleinstalled as well as other prerequisites verified.7.Select the Azure subscription that is in scope for the assessment:8.An internet browser prompt will appear for Azure portal login with Global Administrator credentials:9.The required application consent read permissions will be displayed:Select accept to complete the application registration.Note: Please refer to Permissions for Microsoft Azure AD Assessment Application for consent details.10.Once everything is complete, the application registration can be viewed in the Azure AD portal and thePowerShell output will state that the Azure AD Application has been successfully created:11.If you encounter issues with setting up the Assessment Application, for example if you do not receive anauthentication prompt please refer to the troubleshooting section in the appendix.Setup the Azure AssessmentWhen you have finished the installation of the Microsoft Management Agent/OMS Gateway, you are ready to setup the Azure Assessment. There are two approaches to setting up the assessment scheduled task depending on whether the scheduled task account will be a managed service account or a user account.Configure with User AccountOn the designated data collection machine, complete the following:1.Open the Windows PowerShell command prompt as an Administrator2.Define the credentials for the assessment to use:o$AzureGlobalReader = Get-Credential3.Run the Add-AzureAssessmentTask command using the parameters below, replacing and <Directory> and<AccountName> with an assessment working directory and assessment scheduled task account name:PS C:\OmsAssessment> Add-AzureAssessmentTask -AADUsername $ername -AADPassword $AzureGlobalReader.password -WorkingDirectory <Directory> -ScheduledTaskUsername <accountname>Note. If the command Add-AzureAssessmentTask is not available, the module is not yet found. It can take some time after installing the agent before it to show up.4.The script will continue with the necessary configuration. It will create a scheduled task that will trigger the datacollection.Scheduled Task DetailsData collection is triggered by the scheduled task named AzureAssessment within an hour of running the previous script and then every 7 days. The task can be modified to run on a different date/time or even forced to run immediately.For guidance and details on working with assessment results, visit Working with Assessment Results in the Services Hub Resource Center.AppendixData Collection MethodsThe Azure Assessment uses a couple data collection methods to collect information from your Azure AD tenant. This section describes the methods used to collect data from your environment. No Microsoft Visual Basic (VB) scripts are used to collect data.1. Windows PowerShell2. Graph API4. Windows PowerShellPowerShell is used extensively in the Azure Assessment to gather configuration data. This includes scripts that directly call Graph API endpoints as well as cmdlets from MSOnline and AzureADPreview modules.5. Graph APIGraph API is used to collect configuration and assessment data from Secure Score.Troubleshooting Azure Assessment SetupGeneral Troubleshooting OnDemand Assessment Guidehttps:///en-us/services-hub/health/assessments-troubleshootingAzure datacenter IP address rangesAzure Assessment requires connectivity to the Internet from the data collection machine or proxy server. The endpoints listed in the following articles should be reachable from the data collection machine for successful assessment setup and execution. These are in addition to those required by Azure Log Analytics and the Microsoft Management Agent.•Public: https:///en-us/download/details.aspx?id=56519•US Gov (including DoD): /en-us/download/details.aspx?id=57063•Germany: /en-us/download/details.aspx?id=57064•China: /en-us/download/details.aspx?id=57062New-MicrosoftAssessmentApplicationIf there are URL restrictions in place in order to correctly setup the Assessment Application, you will need to ensure you whitelist the following URLs::443:443:443:443:443Along with above URLs, ensure the following settings are enabled in Internet Explorer as JavaScript needs to run on the page. Internet Options Security SettingsWhile executing the New-MicrosoftAssessmentsApplication command, you may be prompted to add additional links to trusted sites to allow the authentication screen to display. These can be added by clicking the “Add” button shown on the popup.Prerequisites ErrorIf you encounter any prerequisites errors, please check for any errors in Event Viewer as shown below:。

<Placeholder cover – we will adjust> Microsoft Azure StackLicensing Guide(end customers)August 20173 3 6 6 8How Azure Stack is purchasedThere are two ways to purchase Azure Stack:1.Purchase Azure Stack services via your own EA2.Purchase Azure Stack services from a service providerThis document provides licensing guidance for running the Azure Stack within your own enterprise. If you purchase Azure Stack services from a service provider, the provider will set the pricing and terms of use and offer support.Azure Stack is sold as an integrated system, meaning that software comes installed on prescribed hardware. A complete Azure Stack system is comprised of hardware, software, and support.Hardware: Hardware is purchased directly from the hardware vendor. A complete list of Azure Stack hardware partners can be found on the Azure Stack product page. If you are purchasing Azure Stack from a service provider, you may not need to purchase your own hardware.Software: You may purchase Azure Stack services via your Microsoft Enterprise Agreement (EA) or from a service provider. This document describes the model for purchasing Azure Stack via Microsoft EA only. When purchasing Azure Stack from a service provider, the service provider will set the terms and prices for the services.Support: If you purchase Azure Stack services from a service provider, your provider will provide support. If you purchase Azure Stack services via your Microsoft EA, support comes in two parts—hardware support and software support.•Hardware support is contracted directly with the hardware partners.•Software support is contracted directly with Microsoft. If you already have software support from Microsoft (Azure or Premier support plans), those contracts cover Azure Stack softwaresupport and no additional contracts or fees are needed. While support is with the hardwarepartner and Microsoft, our integrated support experience provides coordinated escalation and resolution, so you get a consistent support experience no matter who you call first. Azure Stack software–packaging and pricingThere are three layers to Azure Stack software: the cloud infrastructure that powers the system, the services running on the system, and portal capabilities. Only services running on the Azure Stack are billed. Services can be licensed in one of two ways as shown in Table 1--a pay-as-you-use (consumption-based) model and a capacity model.Table 1: Licensing ModelsPay-as-you-useThe pay-as-you-use model has no up-front fees and you pay only when you use a service, as shown in Table 2. This model offers a continuous transaction experience with Azure. Usage for each service is metered and transmitted to Microsoft Azure commerce, where the information is integrated and billed with your Azure usage.There is no initial deployment fee for pay-as-you use. Additionally, you are not charged for the virtual machines and software required to power the Azure Stack infrastructure. This means that Cloud Infrastructure, Management, Security, and Identity Services, as well as Networking and Service Fabric are not charged. The following describes the units of metering for the services available on Azure Stack at general availability. All services are entirely stand-alone. For example, when you run App Service, you are only spinning App Service meters.Table 2. Azure Stack Pay-as-You-Use Metering UnitsUp-Front Licensing Azure Stack initial deployment n/a – no upfront feesConsumption-Based Fees Cloud infrastructure; Management, Security, andIdentity; Networking; Service Fabricn/a – includedVirtual Machines: Base VM $/VCPU/minVirtual Machines: with Windows Server $/VCPU/minBlog Storage Service $/GB (no transaction fee) Tables and Queues Service $/GB (no transaction fee) Azure App Service $/VCPU/minTo run Windows Server virtual machines, you have the option of either using the native meters within Azure Stack or deploying existing Windows Server licenses in conjunction with the Azure Stack Base VM hourly meters. To run SQL Server virtual machines, you may deploy existing licenses in conjunction with Windows virtual machines. Details for how existing licenses work in conjunction with Azure Stack can be found in the “Using existing software” section of this document.Azure Stack pay-as-you-use services are available in EA and are sold in the same way as Azure services. This means Azure Stack is acquired via a monetary commit SKU on your Azure or SCE enrollment. You can use the same agreement, pool of monetary commit, and subscription IDs for your Azure and Azure Stack services. If you have an existing Azure agreement, you don’t need any additional agreemen ts or monetary commitment purchases—you need only enter your subscription ID when you install the system. Your Azure Stack usage will be metered and integrated into one bill with your Azure usage.Capacity ModelThe capacity model offers a more traditional licensing model for disconnected scenarios, as shown in Table 3. An annual subscription fee licenses all the physical cores on your Azure Stack. The capacity model is available in an App Service package or an IaaS package. The App Service package includes all the services on the IaaS package, plus Azure App Service (including Web, Mobile, Logic Apps, and Functions).Table 3. Azure Stack Capacity Model—Licensing Packages$/physical core/year$/physical core/yearAzure App ServiceAzure StorageBase Virtual MachineWindows VirtualBYO License BYO LicenseMachineSQL Server VirtualBYO License BYO LicenseMachineYou need existing Windows Server or SQL Server licenses to run Windows Server and SQL Server virtual machines on the capacity model. Details on how existing licensing works in conjunction with Azure Stack are discussed in “Using existing software” section of this document.The capacity model is available in EA only and can be ordered via standard Volume Licensing channels. The capacity model will not have integrated billing with Azure and Azure monetary commitment cannot be applied to the capacity model.Azure Stack supportAzure Stack support is a consistent, integrated, hybrid support experience that covers the full system lifecycle. To fully support your Azure Stack system, you need two support instruments—one with Microsoft for cloud services support and one with your hardware provider for system support. Our integrated support experience provides coordinated escalation and resolution, so you get a consistent support experience no matter who you call first. If you already have Premier, Azure, or Partner support with Microsoft, your Azure Stack software support is included.Although support is purchased in separate components, Microsoft and the hardware providers have partnered to create a unified support experience. You need only make one call to the vendor of your choice (Microsoft or hardware partner) for any Azure Stack issue. That vendor will help you diagnose the source of the issue and route your question accordingly.Using existing software with Azure StackCustomers may use existing software licenses (e.g., Windows Server, SQL Server, Marketplace services) in conjunction with Azure Stack. Azure Stack is treated like on-premises hardware for purposes oflicensing existing software. Customers must comply with all product licensing terms under which the software is acquired. When other software is used in conjunction with Azure Stack, the fee structure is:Licensing fees for the software (paid to the software vendor) + virtual machines consumed to run the serviceGuidelines for how Microsoft Windows Server and SQL Server licensing are applied to Azure Stack systems are discussed in the following sections.Windows Server licensingWhen deploying Windows Server virtual machines on Azure Stack, you may use existing Windows Server licenses as an alternative to the native hourly Windows Server meters in the pay-as-you-use model. Windows Server licenses acquired apart from Azure Stack are subject to terms and conditions stated in the Microsoft Product Terms.What follows are some guidelines for how the licensing terms and conditions can be applied when existing Window Server licenses are used with Azure Stack:1.Number of licenses required for Windows Server used with Azure StackTo comply with Windows Server licensing, all cores in an Azure Stack region must be covered, just like when licensing Hyper-V. Furthermore, all cores must be covered with the same edition of license (all Datacenter or all Standard), since the virtual machine may be sitting anywhere on the Azure Stack. We recommend Windows Server Datacenter for Azure Stack, since weanticipate your workloads will be heavily virtualized. You can use EA, Open, or Select PlusWindows Server licenses. Customers using volume licensing licenses must also have sufficientCALs to cover the use case. Since Azure Stack is on your own hardware, you do not need Azure Hybrid Use Benefit (AHUB) rights to use Windows Server in conjunction with Azure Stack.2.AHUB with Azure StackAzure Stack is considered on-premises hardware for licensing purposes. As such, you do notneed AHUB to use existing Windows Server licenses in conjunction with dedicated Azure Stack environments. Furthermore, the AHUB benefit does not extend to bringing Windows Server EA licenses to hosted, multi-tenant environments; you may not bring Windows Server EA licenses to such environments.SQL Server licensingSQL Server virtual machines can be deployed on Azure Stack by using separately acquired SQL Server licenses in conjunction with Windows virtual machines. SQL Server licenses acquired outside Azure Stack are subject to Microsoft Product Terms.What follows are some guidelines that illustrate how licensing terms and conditions are applied when existing SQL Server licenses are used with Azure Stack:1.Number of core licenses required for SQL Server used with Azure StackSQL Server may be licensed either by physical cores or by virtual machines. If licensing byphysical cores, you must license the entire Azure Stack region1. If licensing by virtual machines, you only need enough licenses to cover the virtual machines using SQL Server (subject to aminimum of 4 per virtual machine). If licensing by virtual machines, you may separately allocate SQL Server Enterprise and Standard edition licenses by virtual machine. Since Azure Stack is the customer’s own hardware, you do not need License Mobility when using SQL Server under EA on your own Azure Stack hardware.2.License MobilityAzure Stack is considered on-premises hardware for licensing purposes. As such, you do notneed License Mobility to use SQL Server licenses in dedicated Azure Stack environments. You will, however, need License Mobility if you bring your own SQL Server EA licenses to a service provider’s multi-tenant hosted environment. In that situation, you must also ensure your service provider is an authorized License Mobility provider.Example scenariosThe following figures and text illustrate a few examples for how services are licensed on Azure Stack, particularly focused on contrasting the licensing for pure Azure Stack meters with scenarios where on-premises licenses are used in conjunction with Azure Stack.If using all native meters, as in Figure 1, you pay only for what you use. Usage is metered on a per minute basis. Storage is decoupled from virtual-machine instances and paid for separately.Figure 1. All Native Azure Stack MetersWhen you use existing licenses to deploy Windows Server virtual machines on Azure Stack, you bring your own license and pay only a consumption rate on Base VM meters. You must have enough Windows Server core licenses to cover the entire Azure Stack region, regardless of how many Windows Server virtual machines are deployed on the Azure Stack. In the scenario shown in Figure 2, 25 of the 75 virtual machine cores (vcores) are using Windows Server. However, since there are 100 physical cores in the system, 100 Windows Server core licenses are needed. When used with existing Windows Server licenses, Azure Stack only runs consumption meters at the Base VM rate for the Windows Server virtual machines.Figure 2. On-Premises License with Azure StackWhen using existing licenses to deploy SQL Server virtual machines on Azure Stack, you pay for those SQL Server licenses, plus Windows virtual machines. In Figure 2, since we’ve already deployed enough separately acquired Windows Server licenses to cover the entire Azure Stack region, only a Base VM fee is metered for the 25 vcores being used for SQL Server virtual machines. If you are only using SQL Server for part of your deployment, you may license it on a per-virtual machine basis. In accordance with SQL Server licensing rules, there is a 4-core licensing minimum per virtual machine. Even if you deploy a 1-node SQL Server virtual machine, you must still pay for and allocate 4 core licenses. DefinitionsAzure Stack region: A region is a logical concept describing a set of physical resources to which workloads can be assigned. The Azure Stack ARM may assign a workload deployed to an Azure Stack region to any of the physical resources within the region. Administrators will configure the boundaries of the region, but regions will have a minimum of 4 physical nodes to ensure redundancy. (At general availability, Azure Stack will support only one region per deployment.)。