Add and Configure Azure Subscriptions for Cloud-Based Apps

To add an Azure subscription, you'll need to sign up for a free account or upgrade an existing one. This will give you access to a wide range of cloud-based services, including computing, storage, and networking.

You can sign up for a free Azure account on the Azure website, which will give you a $200 credit to use for the first 30 days. This is a great way to try out Azure and see if it's a good fit for your needs.

Azure subscriptions can be added in the Azure portal, which is the main interface for managing your Azure resources. From the portal, you can view and manage your subscriptions, as well as access other Azure services.

To configure your Azure subscription, you'll need to set up a payment method, such as a credit card or bank account. This will allow you to pay for any services you use beyond the free credit.

You might like: What Is a Azure Subscription

To set up your Azure subscription, you'll need to associate it with your Microsoft Entra ID. To do this, sign in to the Azure portal with the Owner role assignment for the subscription.

You can change the directory for your subscription by selecting Change directory on the subscription page. This will take several hours to complete, so be patient. If you need to troubleshoot, check the Global subscription filter to ensure the moved subscription isn't hidden.

To add a Microsoft Azure subscription, you'll need to enter some basic information. This includes the Directory (tenant) ID, Subscription ID, Subscription name (optional), and Description (optional). You can find these details in the Azure portal.

Here's a breakdown of the required fields:

After entering the subscription details, click Save and continue to Configuration.

You can configure Azure services by setting up a subscription, which is a billing and account management resource.

Azure services can be configured to use a resource group, which is a logical container for related resources.

To configure Azure services, you'll also need to set up a storage account, which is a place to store and manage data.

On a similar theme: Azure Resource

To associate a subscription with a directory, you need to sign in to the Azure portal with the Owner role assignment for the subscription. This is a crucial step that sets the foundation for the process.

You'll then need to browse to Subscriptions, select the name of the subscription you want to use, and choose Change directory. Be aware that changing the subscription directory is a service-level operation, so it doesn't affect subscription billing ownership.

After selecting Change, you'll get a success message indicating that the directory has been changed for the subscription. However, it can take several hours for everything to show up properly.

To ensure a smooth transition, check the Global subscription filter to make sure the moved subscription isn't hidden. If it is, you may need to sign out of the Azure portal and sign back in to see the new directory.

Here are the steps to associate a subscription with a directory:

To configure Microsoft as an identity provider, you'll need to sign in to the Azure portal with an account that has at least External Identity Provider Administrator privileges.

First, ensure you're in the correct Azure AD B2C tenant by selecting the Settings icon in the top menu and switching to your Azure AD B2C tenant from the Directories + subscriptions menu.

Next, choose All services in the top-left corner of the Azure portal and search for Azure AD B2C.

Select Identity providers, then Microsoft Account, and enter a name for your provider, such as MSA.

You'll need to enter the Application (client) ID of the Microsoft Entra application you created earlier for the Client ID.

For the Client secret, enter the client secret that you recorded.

Once you've entered all the required information, select Save to complete the configuration.

Broaden your view: Azure Auth Json Website Azure Ad Authentication

Configuring optional claims is a crucial step in integrating Microsoft Entra ID with your Azure AD B2C application. You can add family_name and given_name claims by configuring optional claims in the Azure portal UI or application manifest.

To do this, sign in to the Azure portal, search for and select Microsoft Entra ID, and then navigate to the Manage section and select App registrations. From there, select the application you want to configure optional claims for and then select Token configuration (preview).

Adding optional claims involves selecting the token type you want to configure and then selecting the optional claims to add. This process is straightforward and can be completed in just a few clicks.

Here's a step-by-step guide to configuring optional claims:

By following these steps, you can easily add family_name and given_name claims to your Azure AD B2C application. This will enable you to access additional user information and enhance the user experience.

Related reading: Add User to Azure Sql Database

To configure the relying party policy, you need to specify the user journey that Azure AD B2C will execute. This is done by finding the DefaultUserJourney element within the relying party policy.

The relying party policy, for example SignUpSignIn.xml, typically has a specific user journey ID. In the case of the CustomSignUpSignIn user journey, the ReferenceId is set to CustomSignUpSignIn.

You'll need to update the ReferenceId to match the user journey ID you added, which in this case is CustomSignUpSignIn. This ensures that Azure AD B2C executes the correct user journey.

Suggestion: Add Azure Ad User to Local Administrators

Publishing Azure Apps is a straightforward process that can be completed in a few simple steps.

You can publish Azure apps using the Azure portal, which is a web-based interface that allows you to manage and deploy your applications.

To publish an app, you'll first need to create a new resource group or use an existing one.

Publishing Azure Apps requires careful consideration of legacy applications.

You can easily migrate on-premises apps to a managed domain. This streamlines management of all applications from your legacy, directory-aware apps alongside your modern cloud apps with a single identity solution.

Legacy applications can be a challenge to manage, especially when it comes to identity and access.

However, with the right tools and approach, you can simplify this process. You can use a single identity solution to manage both legacy and modern cloud apps.

This approach makes it easier to maintain consistency and reduce complexity.

By doing so, you can focus on other important tasks, such as improving user experience and enhancing app functionality.

Additional reading: Azure Identity

Publishing your Office Add-in web app to Azure is a straightforward process. You'll need to open your add-in project in Visual Studio and right-click (or select and hold) the web project to choose Publish.

Follow the instructions at Publish your web app. This will guide you through the publishing process. Be sure to select the Visual Studio button at the top of the page.

Visual Studio will publish the web project for your Office Add-in to your Azure web app. This process may take a few minutes to complete. Once it's finished, your browser will open and show a webpage with the text "Your web app is running and waiting for your content."

You'll need to copy the root URL of your web app, which will be in the format https://YourDomain.azurewebsites.net. You'll need this URL later when you edit your add-in manifest file.

Related reading: Azure App Insights vs Azure Monitor

To add a Microsoft Azure subscription, you'll need to provide some essential information. This includes the Directory (tenant) ID, which is in GUID format and represents the Azure directory where the subscription is located.

The Subscription ID is also required, and it's in GUID format, identifying the subscription you're adding. You can also give the subscription a name in SIA for context, although this is optional.

A description is also optional, but it can provide additional useful information about the subscription. After you've entered this information, click Save and continue to Configuration.

Here are the specific fields you'll need to fill out: