Creating an Azure Application Instance

Important: For every new 1st Tier Partner, a separate Azure application instance must be created.

To be able to use the Azure application, first you should create a new application instance.

1. In provider control panel, go to Services > Applications and click the Azure Cloud Solution Provider integration package that you have imported before.
2. Open the Instances tab and click Add Instance.
3. Specify the Application API end-point URI – URI with the corresponding backnet IP: https://<azure_site_ip_backnet_address>:10443/azure/aps/.
4. Click Next.
5. Specify the following global settings:
   • Partner Tenant Name – name of the partner tenant as registered in Microsoft Azure. For example, provider.onmicrosoft.com (for Microsoft Cloud) or provider.onmicrosoft.de (for Microsoft Cloud Germany).
   • OAuth Client ID – unique identifier of an application in Azure. Refer to the Preparing CSP Account InformationIn this section you will learn how to obtain the CSP account information necessary for the successful Azure integration.Make sure you have a CSP agreement with Microsoft as a 1st Tier Partner and credentials to log in to Partner center.Creating an Admin UserCreate a separate admin user in your CSP account. This admin user will be used by Odin Automation for managing Azure services. The Assists your customers as setting of the admin user must be set to the Admin agent value. Note that the login of the admin user must be based on the domain:onmicrosoft.com (for Microsoft Cloud)onmicrosoft.de (for Microsoft Cloud Germany)We recommend that you use the following user name and login: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com (for Microsoft Cloud)Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.de (for Microsoft Cloud Germany)To specify the Assists your customers as setting, you can use the following instruction:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account settings > User management.Click the required admin user.Set Assists your customers as to Admin agent.Click Update.After creating the admin user, write down the admin's username and password because you will need to use them later.Adding a Web AppTo access the Partner Center API:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new web app.Write down the app registration information (App ID, Key). This information will be used by the Azure application for authentication in the Microsoft Cloud.Important: The key expires in 12 or 24 months after its generation (the duration of the key is chosen when it is generated). You must regenerate the key and update it in the global settings of the application before it expires.You will use the copied IDs as the OAuth Client ID and OAuth Secret Key parameters while creating an Azure application instance.Adding a Native AppTo access the Partner Center SDK:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new native app.Copy the ID in the App ID field.You will use the copied ID as the ID of Native Client for Partner Center SDK parameter while creating an Azure application instance.Setting Up a Native App for Access to the ARM APIThis section explains how to set up an Azure AD Application for accessing the ARM APIs to perform operations on Azure CSP subscriptions of CSP customers. The Azure AD Application authentication can be App-only or App + User. This section shows the setup for the App + User-based authentication using a Native App.The following prerequisites must be met:You must have the Global Admin permissions in the CSP Partner’s Azure Active Directory. You need to have a Windows client or server machine with Azure Active Directory PowerShell module version 2 installed. Note: For installation instructions, refer to https://www.powershellgallery.com/packages/AzureAD/2.0.0.98. Also note that the Install-Module -Name AzureAD command works on Windows 10. If your machine runs Windows 8 / 8.1, you should install PackageManagement PowerShell Modules Preview (https://www.microsoft.com/en-us/download/details.aspx?id=51451) beforehand.To register a new Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click Add.On the Create blade, enter a Name for the application. In this example, CSPARMNativeApp is the name of the application. Select Native in Application Type. Provide a Redirect URI, for example, https://MyCSPARMNativeApp.When finished, click Create.To add an ARM API permission for the Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, from the list, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Add. On the Add API access blade, click Select an API.On the Select an API blade, click Windows Azure Service Management API. Click Select to continue.On the Enable Access blade, check Access Azure Service Management as organization users (preview). Click Select to continue.On the Add API access blade, click Done.On the blade for the registered application, below Object ID, click Click to copy to copy the Object ID associated with the registered application. Save this ID as you will need to use it later.If you plan to support Microsoft Cloud Germany, additionally, do the following:Sign in to the Azure portal (https://portal.microsoftazure.de).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Windows Azure Active Directory.On the Enable Access blade, in Delegated permissions, select these permissions:Access the directory as the signed-in userRead all groupsRead all users' basic profilesRead all users' full profilesRead and write all groupsSign in and read user profileClick Save. To configure a pre-consent for a registered application:On a machine that has Azure Active Directory PowerShell module version 2 installed, open a Windows PowerShell command prompt session.For Microsoft Cloud, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureADFor Microsoft Cloud Germany, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureAD -AzureEnvironment "AzureGermanyCloud"When prompted, specify your credentials.Modify the PowerShell script given below by specifying the Object ID of the application registered earlier.#Specify the Application Object Id of the Native App$appObjectId = 'APPLICATION-OBJECT-ID-HERE'Set-AzureADApplication -ObjectId $appObjectId -AvailableToOtherTenants $true$azureADApp = Get-AzureADApplication -ObjectId $appObjectId#Get the Service Principal for the Application object$servicePrincipal = Get-AzureADServicePrincipal -All $true | ? {$_.AppId -eq $azureADApp.AppId}#Get the Admin Agents Group object$adminAgentsGroup = Get-AzureADGroup -All $true | ? {$_.DisplayName -eq 'AdminAgents'}#Run the below command to add preconsent for the applicationAdd-AzureADGroupMember -ObjectId $adminAgentsGroup.ObjectId -RefObjectId $servicePrincipal.ObjectIdExecute the modified script to configure a pre-consent for the application. topic to learn how to get this ID.
   • OAuth Secret Key – secret key of an application in Azure. Refer to the Preparing CSP Account InformationIn this section you will learn how to obtain the CSP account information necessary for the successful Azure integration.Make sure you have a CSP agreement with Microsoft as a 1st Tier Partner and credentials to log in to Partner center.Creating an Admin UserCreate a separate admin user in your CSP account. This admin user will be used by Odin Automation for managing Azure services. The Assists your customers as setting of the admin user must be set to the Admin agent value. Note that the login of the admin user must be based on the domain:onmicrosoft.com (for Microsoft Cloud)onmicrosoft.de (for Microsoft Cloud Germany)We recommend that you use the following user name and login: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com (for Microsoft Cloud)Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.de (for Microsoft Cloud Germany)To specify the Assists your customers as setting, you can use the following instruction:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account settings > User management.Click the required admin user.Set Assists your customers as to Admin agent.Click Update.After creating the admin user, write down the admin's username and password because you will need to use them later.Adding a Web AppTo access the Partner Center API:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new web app.Write down the app registration information (App ID, Key). This information will be used by the Azure application for authentication in the Microsoft Cloud.Important: The key expires in 12 or 24 months after its generation (the duration of the key is chosen when it is generated). You must regenerate the key and update it in the global settings of the application before it expires.You will use the copied IDs as the OAuth Client ID and OAuth Secret Key parameters while creating an Azure application instance.Adding a Native AppTo access the Partner Center SDK:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new native app.Copy the ID in the App ID field.You will use the copied ID as the ID of Native Client for Partner Center SDK parameter while creating an Azure application instance.Setting Up a Native App for Access to the ARM APIThis section explains how to set up an Azure AD Application for accessing the ARM APIs to perform operations on Azure CSP subscriptions of CSP customers. The Azure AD Application authentication can be App-only or App + User. This section shows the setup for the App + User-based authentication using a Native App.The following prerequisites must be met:You must have the Global Admin permissions in the CSP Partner’s Azure Active Directory. You need to have a Windows client or server machine with Azure Active Directory PowerShell module version 2 installed. Note: For installation instructions, refer to https://www.powershellgallery.com/packages/AzureAD/2.0.0.98. Also note that the Install-Module -Name AzureAD command works on Windows 10. If your machine runs Windows 8 / 8.1, you should install PackageManagement PowerShell Modules Preview (https://www.microsoft.com/en-us/download/details.aspx?id=51451) beforehand.To register a new Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click Add.On the Create blade, enter a Name for the application. In this example, CSPARMNativeApp is the name of the application. Select Native in Application Type. Provide a Redirect URI, for example, https://MyCSPARMNativeApp.When finished, click Create.To add an ARM API permission for the Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, from the list, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Add. On the Add API access blade, click Select an API.On the Select an API blade, click Windows Azure Service Management API. Click Select to continue.On the Enable Access blade, check Access Azure Service Management as organization users (preview). Click Select to continue.On the Add API access blade, click Done.On the blade for the registered application, below Object ID, click Click to copy to copy the Object ID associated with the registered application. Save this ID as you will need to use it later.If you plan to support Microsoft Cloud Germany, additionally, do the following:Sign in to the Azure portal (https://portal.microsoftazure.de).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Windows Azure Active Directory.On the Enable Access blade, in Delegated permissions, select these permissions:Access the directory as the signed-in userRead all groupsRead all users' basic profilesRead all users' full profilesRead and write all groupsSign in and read user profileClick Save. To configure a pre-consent for a registered application:On a machine that has Azure Active Directory PowerShell module version 2 installed, open a Windows PowerShell command prompt session.For Microsoft Cloud, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureADFor Microsoft Cloud Germany, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureAD -AzureEnvironment "AzureGermanyCloud"When prompted, specify your credentials.Modify the PowerShell script given below by specifying the Object ID of the application registered earlier.#Specify the Application Object Id of the Native App$appObjectId = 'APPLICATION-OBJECT-ID-HERE'Set-AzureADApplication -ObjectId $appObjectId -AvailableToOtherTenants $true$azureADApp = Get-AzureADApplication -ObjectId $appObjectId#Get the Service Principal for the Application object$servicePrincipal = Get-AzureADServicePrincipal -All $true | ? {$_.AppId -eq $azureADApp.AppId}#Get the Admin Agents Group object$adminAgentsGroup = Get-AzureADGroup -All $true | ? {$_.DisplayName -eq 'AdminAgents'}#Run the below command to add preconsent for the applicationAdd-AzureADGroupMember -ObjectId $adminAgentsGroup.ObjectId -RefObjectId $servicePrincipal.ObjectIdExecute the modified script to configure a pre-consent for the application. topic to learn how to get this key.
   • ID of Native Client for Partner Center SDK – refer to the Preparing CSP Account InformationIn this section you will learn how to obtain the CSP account information necessary for the successful Azure integration.Make sure you have a CSP agreement with Microsoft as a 1st Tier Partner and credentials to log in to Partner center.Creating an Admin UserCreate a separate admin user in your CSP account. This admin user will be used by Odin Automation for managing Azure services. The Assists your customers as setting of the admin user must be set to the Admin agent value. Note that the login of the admin user must be based on the domain:onmicrosoft.com (for Microsoft Cloud)onmicrosoft.de (for Microsoft Cloud Germany)We recommend that you use the following user name and login: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com (for Microsoft Cloud)Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.de (for Microsoft Cloud Germany)To specify the Assists your customers as setting, you can use the following instruction:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account settings > User management.Click the required admin user.Set Assists your customers as to Admin agent.Click Update.After creating the admin user, write down the admin's username and password because you will need to use them later.Adding a Web AppTo access the Partner Center API:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new web app.Write down the app registration information (App ID, Key). This information will be used by the Azure application for authentication in the Microsoft Cloud.Important: The key expires in 12 or 24 months after its generation (the duration of the key is chosen when it is generated). You must regenerate the key and update it in the global settings of the application before it expires.You will use the copied IDs as the OAuth Client ID and OAuth Secret Key parameters while creating an Azure application instance.Adding a Native AppTo access the Partner Center SDK:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new native app.Copy the ID in the App ID field.You will use the copied ID as the ID of Native Client for Partner Center SDK parameter while creating an Azure application instance.Setting Up a Native App for Access to the ARM APIThis section explains how to set up an Azure AD Application for accessing the ARM APIs to perform operations on Azure CSP subscriptions of CSP customers. The Azure AD Application authentication can be App-only or App + User. This section shows the setup for the App + User-based authentication using a Native App.The following prerequisites must be met:You must have the Global Admin permissions in the CSP Partner’s Azure Active Directory. You need to have a Windows client or server machine with Azure Active Directory PowerShell module version 2 installed. Note: For installation instructions, refer to https://www.powershellgallery.com/packages/AzureAD/2.0.0.98. Also note that the Install-Module -Name AzureAD command works on Windows 10. If your machine runs Windows 8 / 8.1, you should install PackageManagement PowerShell Modules Preview (https://www.microsoft.com/en-us/download/details.aspx?id=51451) beforehand.To register a new Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click Add.On the Create blade, enter a Name for the application. In this example, CSPARMNativeApp is the name of the application. Select Native in Application Type. Provide a Redirect URI, for example, https://MyCSPARMNativeApp.When finished, click Create.To add an ARM API permission for the Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, from the list, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Add. On the Add API access blade, click Select an API.On the Select an API blade, click Windows Azure Service Management API. Click Select to continue.On the Enable Access blade, check Access Azure Service Management as organization users (preview). Click Select to continue.On the Add API access blade, click Done.On the blade for the registered application, below Object ID, click Click to copy to copy the Object ID associated with the registered application. Save this ID as you will need to use it later.If you plan to support Microsoft Cloud Germany, additionally, do the following:Sign in to the Azure portal (https://portal.microsoftazure.de).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Windows Azure Active Directory.On the Enable Access blade, in Delegated permissions, select these permissions:Access the directory as the signed-in userRead all groupsRead all users' basic profilesRead all users' full profilesRead and write all groupsSign in and read user profileClick Save. To configure a pre-consent for a registered application:On a machine that has Azure Active Directory PowerShell module version 2 installed, open a Windows PowerShell command prompt session.For Microsoft Cloud, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureADFor Microsoft Cloud Germany, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureAD -AzureEnvironment "AzureGermanyCloud"When prompted, specify your credentials.Modify the PowerShell script given below by specifying the Object ID of the application registered earlier.#Specify the Application Object Id of the Native App$appObjectId = 'APPLICATION-OBJECT-ID-HERE'Set-AzureADApplication -ObjectId $appObjectId -AvailableToOtherTenants $true$azureADApp = Get-AzureADApplication -ObjectId $appObjectId#Get the Service Principal for the Application object$servicePrincipal = Get-AzureADServicePrincipal -All $true | ? {$_.AppId -eq $azureADApp.AppId}#Get the Admin Agents Group object$adminAgentsGroup = Get-AzureADGroup -All $true | ? {$_.DisplayName -eq 'AdminAgents'}#Run the below command to add preconsent for the applicationAdd-AzureADGroupMember -ObjectId $adminAgentsGroup.ObjectId -RefObjectId $servicePrincipal.ObjectIdExecute the modified script to configure a pre-consent for the application. topic to learn how to get this ID.
   • ID of Native Client for Azure Resource Management API – refer to the Preparing CSP Account InformationIn this section you will learn how to obtain the CSP account information necessary for the successful Azure integration.Make sure you have a CSP agreement with Microsoft as a 1st Tier Partner and credentials to log in to Partner center.Creating an Admin UserCreate a separate admin user in your CSP account. This admin user will be used by Odin Automation for managing Azure services. The Assists your customers as setting of the admin user must be set to the Admin agent value. Note that the login of the admin user must be based on the domain:onmicrosoft.com (for Microsoft Cloud)onmicrosoft.de (for Microsoft Cloud Germany)We recommend that you use the following user name and login: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com (for Microsoft Cloud)Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.de (for Microsoft Cloud Germany)To specify the Assists your customers as setting, you can use the following instruction:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account settings > User management.Click the required admin user.Set Assists your customers as to Admin agent.Click Update.After creating the admin user, write down the admin's username and password because you will need to use them later.Adding a Web AppTo access the Partner Center API:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new web app.Write down the app registration information (App ID, Key). This information will be used by the Azure application for authentication in the Microsoft Cloud.Important: The key expires in 12 or 24 months after its generation (the duration of the key is chosen when it is generated). You must regenerate the key and update it in the global settings of the application before it expires.You will use the copied IDs as the OAuth Client ID and OAuth Secret Key parameters while creating an Azure application instance.Adding a Native AppTo access the Partner Center SDK:Log in to the Partner Center (https://partnercenter.microsoft.com/).Go to Account setting > App management and click Add new native app.Copy the ID in the App ID field.You will use the copied ID as the ID of Native Client for Partner Center SDK parameter while creating an Azure application instance.Setting Up a Native App for Access to the ARM APIThis section explains how to set up an Azure AD Application for accessing the ARM APIs to perform operations on Azure CSP subscriptions of CSP customers. The Azure AD Application authentication can be App-only or App + User. This section shows the setup for the App + User-based authentication using a Native App.The following prerequisites must be met:You must have the Global Admin permissions in the CSP Partner’s Azure Active Directory. You need to have a Windows client or server machine with Azure Active Directory PowerShell module version 2 installed. Note: For installation instructions, refer to https://www.powershellgallery.com/packages/AzureAD/2.0.0.98. Also note that the Install-Module -Name AzureAD command works on Windows 10. If your machine runs Windows 8 / 8.1, you should install PackageManagement PowerShell Modules Preview (https://www.microsoft.com/en-us/download/details.aspx?id=51451) beforehand.To register a new Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click Add.On the Create blade, enter a Name for the application. In this example, CSPARMNativeApp is the name of the application. Select Native in Application Type. Provide a Redirect URI, for example, https://MyCSPARMNativeApp.When finished, click Create.To add an ARM API permission for the Azure AD native application:Sign in to the Azure portal (https://portal.azure.com for Microsoft Cloud or https://portal.microsoftazure.de for Microsoft Cloud Germany).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, from the list, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Add. On the Add API access blade, click Select an API.On the Select an API blade, click Windows Azure Service Management API. Click Select to continue.On the Enable Access blade, check Access Azure Service Management as organization users (preview). Click Select to continue.On the Add API access blade, click Done.On the blade for the registered application, below Object ID, click Click to copy to copy the Object ID associated with the registered application. Save this ID as you will need to use it later.If you plan to support Microsoft Cloud Germany, additionally, do the following:Sign in to the Azure portal (https://portal.microsoftazure.de).In the left-hand navigation pane, select More services and click App registrations.On the App registrations blade, click the application that you registered earlier.On the blade for the registered application, click All settings. On the Settings blade, click Required permissions.On the Required permissions blade, click Windows Azure Active Directory.On the Enable Access blade, in Delegated permissions, select these permissions:Access the directory as the signed-in userRead all groupsRead all users' basic profilesRead all users' full profilesRead and write all groupsSign in and read user profileClick Save. To configure a pre-consent for a registered application:On a machine that has Azure Active Directory PowerShell module version 2 installed, open a Windows PowerShell command prompt session.For Microsoft Cloud, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureADFor Microsoft Cloud Germany, run the following cmdlet to connect to the Azure Active Directory:Connect-AzureAD -AzureEnvironment "AzureGermanyCloud"When prompted, specify your credentials.Modify the PowerShell script given below by specifying the Object ID of the application registered earlier.#Specify the Application Object Id of the Native App$appObjectId = 'APPLICATION-OBJECT-ID-HERE'Set-AzureADApplication -ObjectId $appObjectId -AvailableToOtherTenants $true$azureADApp = Get-AzureADApplication -ObjectId $appObjectId#Get the Service Principal for the Application object$servicePrincipal = Get-AzureADServicePrincipal -All $true | ? {$_.AppId -eq $azureADApp.AppId}#Get the Admin Agents Group object$adminAgentsGroup = Get-AzureADGroup -All $true | ? {$_.DisplayName -eq 'AdminAgents'}#Run the below command to add preconsent for the applicationAdd-AzureADGroupMember -ObjectId $adminAgentsGroup.ObjectId -RefObjectId $servicePrincipal.ObjectIdExecute the modified script to configure a pre-consent for the application. section to learn how to get this ID.
   • Partner Admin User Name – login name of the Partner admin.
   • Partner Admin Password – password of the Partner admin.
   • Partner relationship link to register new customers – a link from this field is displayed in purchase wizards of online store, OA Billing panel and marketplace if a customer tries to purchase a subscription into an existent tenant that was initially created under another CSP Partner. By leaving this field empty, the link to the instruction of how to use a tenant under another Partner is generated automatically and leads to Microsoft site. However, you can provide here any custom link that would lead to your own site. Read more in Customizing a Partner Relationship Link.
   • Offer ID – Offer ID that works as input for placing the order for the offer. It is "MS-AZR-0145P" ("MS-AZR-DE-0145P" for Microsoft Cloud Germany) for production provisioning now, but it can be changed in the future. Check it with your contact person in Microsoft when you sign the partner agreement.

     Note: The ID "MS-AZR-0145P" ("MS-AZR-DE-0145P" for Microsoft Cloud Germany) is used to provision a production Azure subscription. However, bear in mind that "MS-AZR-0146P" ("MS-AZR-DE-0146P" for Microsoft Cloud Germany) should be used instead when provisioning to a sandbox.

6. Click Next.
7. Validate the parameters carefully and click Finish.

You can later edit these data in Services > Applications > Azure Cloud Solution Provider > Instances > <instance name> > Configuration tab.