github.com/recobe182/terraform@v0.8.5-0.20170117231232-49ab22a935b7/website/source/docs/providers/azurerm/index.html.markdown (about)

     1  ---
     2  layout: "azurerm"
     3  page_title: "Provider: Azure Resource Manager"
     4  sidebar_current: "docs-azurerm-index"
     5  description: |-
     6    The Azure Resource Manager provider is used to interact with the many resources supported by Azure, via the ARM API. This supercedes the Azure provider, which interacts with Azure using the Service Management API. The provider needs to be configured with a credentials file, or credentials needed to generate OAuth tokens for the ARM API.
     7  ---
     8  
     9  # Microsoft Azure Provider
    10  
    11  The Microsoft Azure provider is used to interact with the many
    12  resources supported by Azure, via the ARM API. This supercedes the [legacy Azure
    13  provider][asm], which interacts with Azure using the Service Management API. The
    14  provider needs to be configured with the credentials needed to generate OAuth
    15  tokens for the ARM API.
    16  
    17  [asm]: /docs/providers/azure/index.html
    18  
    19  Use the navigation to the left to read about the available resources.
    20  
    21  ## Example Usage
    22  
    23  ```
    24  # Configure the Microsoft Azure Provider
    25  provider "azurerm" {
    26    subscription_id = "..."
    27    client_id       = "..."
    28    client_secret   = "..."
    29    tenant_id       = "..."
    30  }
    31  
    32  # Create a resource group
    33  resource "azurerm_resource_group" "production" {
    34      name     = "production"
    35      location = "West US"
    36  }
    37  
    38  # Create a virtual network in the web_servers resource group
    39  resource "azurerm_virtual_network" "network" {
    40    name                = "productionNetwork"
    41    address_space       = ["10.0.0.0/16"]
    42    location            = "West US"
    43    resource_group_name = "${azurerm_resource_group.production.name}"
    44  
    45    subnet {
    46      name           = "subnet1"
    47      address_prefix = "10.0.1.0/24"
    48    }
    49  
    50    subnet {
    51      name           = "subnet2"
    52      address_prefix = "10.0.2.0/24"
    53    }
    54  
    55    subnet {
    56      name           = "subnet3"
    57      address_prefix = "10.0.3.0/24"
    58    }
    59  }
    60  
    61  ```
    62  
    63  ## Argument Reference
    64  
    65  The following arguments are supported:
    66  
    67  * `subscription_id` - (Optional) The subscription ID to use. It can also
    68    be sourced from the `ARM_SUBSCRIPTION_ID` environment variable.
    69  
    70  * `client_id` - (Optional) The client ID to use. It can also be sourced from
    71    the `ARM_CLIENT_ID` environment variable.
    72  
    73  * `client_secret` - (Optional) The client secret to use. It can also be sourced from
    74    the `ARM_CLIENT_SECRET` environment variable.
    75  
    76  * `tenant_id` - (Optional) The tenant ID to use. It can also be sourced from the
    77    `ARM_TENANT_ID` environment variable.
    78  
    79  * `environment` - (Optional) The cloud environment to use. It can also be sourced
    80    from the `ARM_ENVIRONMENT` environment variable. Supported values are:
    81    * `public` (default)
    82    * `usgovernment`
    83    * `german`
    84    * `china`
    85    
    86  * `skip_provider_registration` - (Optional) Prevents the provier from registering
    87    the ARM provider namespaces, this can be used if you don't wish to give the Active
    88    Directory Application permission to register resource providers. It can also be
    89    sourced from the `ARM_SKIP_PROVIDER_REGISTRATION` environment variable, defaults
    90    to `false`.
    91  
    92  ## Creating Credentials
    93  
    94  Azure requires that an application is added to Azure Active Directory to generate the `client_id`, `client_secret`, and `tenant_id` needed by Terraform (`subscription_id` can be recovered from your Azure account details).
    95  
    96  There are two high-level tasks to complete.  The first is to create an App Registration with Azure Active Directory.  You can do this in either the New ARM portal (http://portal.azure.com) or the older 'Classic' portal (http://manage.windowsazure.com).
    97  
    98  The second task is to grant permissions for the Application Registration in your Subscription.
    99  
   100  To create the App Registration using the New ARM portal:
   101  
   102  - Select **Azure Active Directory** from the left pane
   103  - Select the **App Registrations** tile from the Overview Section
   104  - Click **Endpoints** at the top of the App Registrations blade.  This will display a list of URIs. Extract the GUID from the bottom URI for **OAUTH 2.0 AUTHORIZATION ENDPOINT**. This is the `tenant_id`
   105  - Select **Add** from the top of the blade.
   106  - Add a friendly name for the application e.g. **Terraform**. Choose **Web App / API** for Application Type
   107  - Add a valid URI as the Sign-on URL. This isn't used and can be anything e.g. http://terra.form.
   108  - Click **Create** at the bottom to create the App Registration
   109  - Choose your new App Registration to show details
   110  - You should now be on the blade for your App Registration.  At the top, notice the "Application ID" GUID.  You'll use this as the `client_id`
   111  - If the Settings blade for your Application Registration is not showing, click on **All Settings**
   112  - Click on **Keys**. Enter a name for your key in **Key description** and choose an expiration duration.  When you click **Save** at the top of the blade, the key value will be displayed.  Once it is displayed, you then use this as the value for `client_secret`. This will disappear once you move off the page
   113  - Click **Required Permissions**.  Click **Add**.  This will allow us to add permission to use the Windows Azure Service Management API to the App Registration.  On Step 1, choose Windows Azure Service Management API.  Click **Select**.  On Step 2, check the box next to "Access Azure Service Management as organization users".  Click **Select**.  Click **Done** to finish adding the permission.
   114  
   115  To create the App Registration using the 'Classic' portal:
   116  
   117  - Select **Active Directory** from the left pane and select the directory you wish to use
   118  - Select **Applications** from the options at the top of the page
   119  - Select **Add** from the bottom of the page. Choose **Add an application my organization is developing**
   120  - Add a friendly name for the application e.g. **Terraform**. Leave **Web Application And/Or Web API** selected and click the arrow for the next page
   121  - Add two valid URIs. These aren't used an can be anything e.g. http://terra.form. Click the arrow to complete the wizard
   122  - You should now be on the page for the application. Click on **Configure** at the top of the page. Scroll down to the middle of the page where you will see the value for `client_id`
   123  - In the **Keys** section of the page, select a suitable duration and click **Save** at the bottom of the page. This will then display the value for `client_secret`. This will disappear once you move off the page
   124  - Click **View Endpoints** at the bottom of the page. This will display a list of URIs. Extract the GUID from the bottom URI for **OAUTH 2.0 AUTHORIZATION ENDPOINT**. This is the `tenant_id`
   125  
   126  To grant permissions to the App Registration to your subscription, you now must to use to the 'ARM' Portal:
   127  
   128  - Select **Subscriptions** from the left panel. Select the subscription that you want to use. In the Subscription details pane, click **Access Control (IAM)**
   129  - Click **Add**.  For Step 1 select an appropriate role for the tasks you want to complete with Terraform. You can find details on the built in roles [here](https://azure.microsoft.com/en-gb/documentation/articles/role-based-access-built-in-roles/)
   130  - Type in the name of the application added in the search box. You need to type this as it won't be shown in the user list. Click on the appropriate user in the list and then click **Select**
   131  - Click **OK** in the **Add Access** panel. The changes will now be saved
   132  
   133  To create using azure cli:
   134  `az` is using the new azure 2.0 cli using python rather than the old nodejs version. You might be able to replace `az` with `azure`.
   135  ```
   136  az login
   137  az account set --name="${SUBSCRIPTION_ID}"
   138  az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/${SUBSCRIPTION_ID}"
   139  ```
   140  
   141  This will output your `client_id`, `client_secret` (password), `sp_name`, and `tenant`. The sp_name or client_id may be used for the `servicePrincipalProfile.servicePrincipalClientId` and the `client_secret` is used for `servicePrincipalProfile.servicePrincipalClientSecret`.
   142  
   143  Confirm your service principal by opening a new shell and run the following commands substituting in `sp_name`, `client_secret`, and `tenant`:
   144  ```
   145  az login --service-principal -u SPNAME -p CLIENTSECRET --tenant TENANT
   146  az vm list-sizes --location westus
   147  ```
   148  
   149  This may be out of date and was based on: [https://github.com/Azure/acs-engine](https://github.com/Azure/acs-engine/blob/417d0d3655aeab0fee784ef6c623ac8333ebb936/docs/serviceprincipal.md#creating-a-service-principal)
   150  
   151  Microsoft have a more complete guide in the Azure documentation: [Create Active Directory application and service principle](https://azure.microsoft.com/en-us/documentation/articles/resource-group-create-service-principal-portal/)
   152  
   153  ## Testing
   154  
   155  Credentials must be provided via the `ARM_SUBSCRIPTION_ID`, `ARM_CLIENT_ID`,
   156  `ARM_CLIENT_SECRET` and `ARM_TENANT_ID` environment variables in order to run
   157  acceptance tests.