Download Deploy apps to Azure and Azure Stack and more Exams Microsoft Access Skills in PDF only on Docsity!
Table of ContentsTable of Contents
Overview
What is Azure Stack?
Quickstarts
Deploy Azure Stack
Tutorials
Enable Virtual Machines
Enable SQL databases
Enable Web Apps
Deploy apps to Azure & Azure Stack
Concepts
What's new
Key features and concepts
POC architecture
Administration basics
How-to guides
Deploy
Prerequisites
Deploy
Activate portals
Register
Connect to Azure Stack
Add default image
Create a test VM
Manage
Region management
Using the portals
Connect to Azure Stack
Set up management environment
Manage updates
Monitor health and alerts
Manage network resources
Manage storage resources
Manage Windows Azure Pack VMs
Security & compliance
Manage RBAC
Add users for Azure AD
Add users for AD FS
Create service principals
Enable multi-tenancy
Offer services
Create plans, offers, and quotas
Offer SQL or MySQL as PaaS
Offer App Service as PaaS
Populate the marketplace
Usage and billing
Use services
Key considerations
Compute
Storage
Network
Key Vault
Build apps
Develop for Azure Stack
Set up development environment
Use policy module
Use templates
Troubleshoot
Known issues
Diagnostics in Azure Stack
Redeploy Azure Stack POC
Reference
PowerShell
What is Azure Stack Technical Preview 3?
5/5/2017 • 1 min to read • Edit Online
Scope of Azure Stack POC
Next steps
Microsoft Azure Stack is a hybrid cloud platform that lets you deliver Azure services from your organization’s datacenter. Microsoft Azure Stack Technical Preview 3 is being made available as a Proof of Concept (POC). Once deployed, the POC is an ideal environment for learning and demonstrating Azure Stack features. It lets you deploy all required components on a single physical machine to create an environment for evaluating key concepts and capabilities, and validating the extensibility model for APIs. Azure Stack POC must not be used as a production environment and should only be used for testing, evaluation, and demonstration. Your deployment of Azure Stack is associated with a single identity provider, like Azure Active Directory or Active Directory Federation Services. You can create multiple users in this directory and assign subscriptions to each user. With all components deployed on the single machine, there are limited physical resources available for tenant resources. This configuration is not intended for scale or performance evaluation. Networking scenarios are limited due to the single host/NIC requirement. Key features and concepts Hybrid Application innovation with Azure and Azure Stack (pdf)
Azure Stack POC deployment quickstart
5/10/2017 • 1 min to read • Edit Online The Azure Stack Proof of Concept (POC) is a testing and development environment that you can deploy to evaluate and demonstrate Azure Stack features and services. To get it up and running, you’ll need to prepare the environment hardware and run some scripts (this will take several hours). After that, you can sign in to the admin and tenant portals to manage Azure Stack and test offers.
- Plan your hardware, software, and network. The computer that hosts the Azure Stack POC (the POC host) must meet hardware, software, and network requirements. You must also choose between using Azure Active Directory or Active Directory Federation Services. Be sure to comply with these prerequisites before starting your deployment so that the installation process runs smoothly.
- Download and extract the deployment package. You can download the deployment package to the POC host or to a another computer. The extracted deployment files take up 60 GB of free disk space, so using another computer can help reduce the hardware requirements for the POC host.
- Prepare the POC host by running the PrepareBootFromVHD.ps1 script. After this step, the POC host will boot to the Cloudbuilder.vhdx (a virtual hard drive that includes a bootable operating system and the Azure Stack install files).
- To start the deployment, run the PowerShell deployment script on the POC host.
- If your Azure Stack deployment uses Azure Active Directory, you must: Activate the administrator and tenant portals. Register Azure Stack with Azure so that you can download Azure marketplace items to Azure Stack. After completing these steps, you’ll have an Azure Stack POC environment with both administrator and tenant portals. Next, you can connect and sign in to the portal. You can then start deploying resource providers, creating offers, and populating the Azure Stack marketplace.
Compute, Network, and Storage services. In this example, we first create a quota for the Compute service. In the Namespace list, select the Microsoft.Compute namespace. d. Choose the location where the quota is defined (for example, 'local'). e. On the Quota Settings item, it says Set the Capacity of Quota. Click this item to configure the quota settings. f. On the Set Quotas blade, you see all the Compute resources for which you can configure limits. Each type has a default value that's associated with it. You can change these values or you can select the Ok button at the bottom of the blade to accept the defaults.
g. After you have configured the values and clicked OK , the Quota Settings item appears as Configured. Click Create to create the Quota resource. You should see a notification indicating that the quota resource is being created. h. After the quota set has been successfully created, you receive a second notification. The Compute service quota is now ready to be associated with a plan. Repeat these steps with the Network and Storage services, and you are ready to create an IaaS plan!
- Create a plan Plans are groupings of one or more services. As a provider, you can create plans to offer to your users. In turn, your users subscribe to your offers to use the plans and services they include. a. In an internet browser, navigate to https://adminportal.local.azurestack.external. b. Sign in to the Azure Stack Portal as a service administrator. Service administrators can create offers and plans, and manage users. c. To create a plan and offer that users can subscribe to, click New > Tenant Offers + Plans > Plan. d. In the New Plan blade, fill in Display Name and Resource Name. The Display Name is the plan's friendly name that users see. Only the admin can see the Resource Name. It's the name that admins use to work with the plan as an Azure Resource Manager resource.
g. Click Quotas , click Microsoft.Storage (local) , and then select the quota you created previously. h. Click Microsoft.Network (local) , and then select the quota you created previously. i. Click Microsoft.Compute (local) , and then select the quota you created previously. j. In the Quotas blade, click OK , and then in the New Plan blade, click Create to create the plan. k. To see your new plan, click All resources , then search for the plan and click its name.
- Create an offer Offers are groups of one or more plans that providers present to users to purchase or subscribe to. a. Sign in to the portal as a service administrator and then click New > Tenant Offers + Plans > Offer. b. In the New Offer blade, fill in Display Name and Resource Name , and then select a new or existing Resource Group. The Display Name is the offer's friendly name. Only the admin can see the Resource Name. It's the name that admins use to work with the offer as an Azure Resource Manager resource.
Add an image e. Click Change State , and then click Public. Before you can provision virtual machines, you must add an image to the Azure Stack marketplace. This example shows you how to add a Windows Server 2016 image, but you can add the image of your choice, including Linux images. If you are operating in a connected scenario and if you have registered your Azure Stack instance with Azure, then you can download the Windows Server 2016 VM image from the Azure Marketplace by using the steps described in the Download marketplace items from Azure to Azure Stack topic. For information about adding different items to the marketplace , see The Azure Stack Marketplace. This step can take almost an hour to complete!
- After deploying Azure Stack, sign in to the MAS-CON01 virtual machine.
- If you haven't downloaded the Windows Server 2016 image already, go to https://www.microsoft.com/en- us/evalcenter/evaluate-windows-server-2016 and download the Windows Server 2016 evaluation. When prompted, select the ISO version of the download. Record the path to the download location, which is used later in these steps.
Import-Module .\Connect\AzureStack.Connect.psm Import-Module .\ComputeAdmin\AzureStack.ComputeAdmin.psm Add-AzureStackAzureRmEnvironment -Name "AzureStackAdmin" -ArmEndpoint "https://adminmanagement.local.azurestack.external" $TenantID = Get-DirectoryTenantID -AADTenantName "<myaadtenant>.onmicrosoft.com" -EnvironmentName AzureStackAdmin $TenantID = Get-DirectoryTenantID ` -ADFS -EnvironmentName AzureStackAdmin $ISOPath = "<Fully_Qualified_Path_to_ISO>"
Store the service administrator account credentials in a variable
$UserName='' $Password=''| ` ConvertTo-SecureString -Force -AsPlainText $Credential=New-Object PSCredential($UserName,$Password)
Add a Windows Server 2016 Evaluation VM Image.
New-Server2016VMImage -ISOPath $ISOPath -TenantId $TenantID -EnvironmentName "AzureStackAdmin" -Net35 $True ` -AzureStackCredentials $Credential
- Open PowerShell ISE as an administrator.
- Install PowerShell for Azure Stack.
- Download the Azure Stack tools from GitHub. Make sure that you download and extract the Azure Stack tool repository to a folder that is NOT under the C:\Windows\System32 directory.
- Import the Azure Stack Connect and ComputeAdmin modules by using the following commands:
- Create the Azure Stack administrator's AzureRM environment by using the following cmdlet:
- Get the GUID value of the Active Directory(AD) user that is used to deploy the Azure Stack. If your Azure Stack environment is deployed by using: a. Azure Active Directory , use the following cmdlet: b. Active Directory Federation Services , use the following cmdlet:
- Add the Windows Server 2016 image to the Azure Stack marketplace by running the New-Server2016VMImage cmdlet. Replace Path_to_ISO with the path to the WS2016 ISO you downloaded. See the Parameters section for information about the allowed parameters. To ensure that the Windows Server 2016 VM image has the latest cumulative update, include the IncludeLatestCU parameter when running the previous cmdlet. When you run the New-Server2016VMImage cmdlet, the output displays a warning message that says, “Unable
c. To view the subscription you created, click More services , click Subscriptions , then click your new subscription. After you subscribe to an offer, refresh the portal to see which services are part of the new subscription.
- Provision a virtual machine Now you can log in to the portal as a user to provision a virtual machine using the subscription. a. On the Azure Stack POC computer, log in to https://portal.local.azurestack.external as a user, and then click New > Virtual machines > Windows Server 2016 Datacenter Eval. b. In the Basics blade, type a Name , User name , and Password. For VM disk type , choose HDD. Choose a Subscription. Create a Resource group , or select an existing one, and then click OK. c. In the Choose a size blade, click A1 Basic , and then click Select. d. In the Settings blade, click Virtual network. In the Choose virtual network blade, click Create new. In the Create virtual network blade, accept all the defaults, and click OK. In the Settings blade, click OK. e. In the Summary blade, click OK to create the virtual machine. f. To see your new virtual machine, click All resources , then search for the virtual machine and click its name.
What you learned in this tutorial: Create an offer Add an image Test the offer Make web, mobile, and API apps available to your Azure Stack users
- Leave the defaults for the fields, or you can use these examples:
- Click Login Settings , enter credentials for the database, and then click OK.
- Click SKU > select the SQL SKU that you created for the SQL Hosting Server > OK.
- Click Create. Database Name : SQLdb Max Size in MB : 100 Subscription : TestSQLOffer Resource Group : SQL-RG In this tutorial, you learned how to: Deploy the SQL Server resource provider Create an offer Test the offer Advance to the next tutorial to learn how to: Make web, mobile, and API apps available to your users
Make web, mobile, and API apps available to your
Azure Stack users
5/10/2017 • 2 min to read • Edit Online
Deploy the App Service resource provider
Create an offer
Test the offer
Subscribe to the offerSubscribe to the offer As an Azure Stack administrator, you can create offers that let your users (tenants) create Azure Functions and web, mobile, and API applications. By providing access to these on-demand, cloud-based apps to your users, you can save them time and resources. To set this up, you will: Deploy the App Service resource provider Create an offer Test the offer
- Prepare the POC host. This includes deploying the SQL Server resource provider, which is required for creating some apps.
- Download the installer and helper scripts.
- Run the helper script to create required certificates.
- Install the App Service resource provider (it will take a couple hours to install and for all the worker roles to appear).
- Validate the installation. As an example, you can create an offer that lets users create DNN web content management systems. It requires the SQL Server service which you already enabled by installing the SQL Server resource provider.
- Set a quota and name it AppServiceQuota. Select Microsoft.Web for the Namespace field. NOTENOTE
- Create a plan. Name it TestAppServicePlan , select the the Microsoft.SQL service, and AppService Quota quota. To let users create other apps, other services might be required in the plan. For example, Azure Functions requires that the plan include the Microsoft.Storage service, while Wordpress requires Microsoft.MySQL.
- Create an offer, name it TestAppServiceOffer and select the TestAppServicePlan plan. Now that you've deployed the App Service resource provider and created an offer, you can sign in as a user, subscribe to the offer, and create an app. For this example, we'll create a DNN Platform content management system. You must first create a SQL database and then the DNN web app.
- Sign in to the Azure Stack portal (https://portal.local.azurestack.external) as a tenant.
- Click Get a subscription > type TestAppServiceSubscription under Display Name > Select an offer > TestAppServiceOffer > Create.
