Create a Custom Connector For Power Automate & Power Apps

July 15, 2024 priyeshwagh777 Azure Functions, Customizations, Microsoft Azure, Microsoft PowerApps, Power Automate, Power Platform azure, custom connector, Dynamics 365, Microsoft Azure, power apps, Power Automate, Power Platform

One of the most important qualities of extending capabilities of any platform is being able to add Custom code and make it available to wider use cases.

In this case, it’s a custom code that is encompassed in a Custom Connector in Power Platform and made available to Power Automate or Power Platform.

Use Case

The purpose of my custom connector is to call my hosted custom code in Power Automate or Power Apps.

For this example, I’ve created a simple Azure Function that just returns a value – just to test the working of the Custom Connector. Of course, your use case is to be able to connect to the hosted app, expect it to process the business logic which you intend to do and return back the results.
So, in my case – my Azure Function will simply greet the name passed to it.

See the Postman test below –

Now, let’s make a Custom Connector that will execute this Azure Function in your Power Automate.

Create Custom Connector in Power Apps / Power Automate

You can either make the Custom Connector from the Power Automate portal or the Power Apps Maker portal, both are the same things. Let’s see this example from Power Apps portal –

In this use case, I’m in a Solution in Power Apps / Power Automate. Open the one in your case since you can’t create a Custom Connector from outside a Solution any longer.
Now you can drop down from New and see in Automation menu that you can create a Custom Connector
Now, you’ll be required to enter the name of the Connector itself and other details like a PNG icon for it, Description etc.
Now, below is the info that I filled in. I’m calling it Data Transporter and have selected an Icon which should make me easy to recognize my connector in Power Automate and Power Apps and enter enter the details of my hosted Azure Function which is authenticated using an API Key.
So, here’s what my info looks like –
Now, when I click on Security after filling all the info, the type of Authentication I used in this case if API Key, yours could be different depending on what your custom application is configured to work with –
It’ll ask you to fill in the information so that it appears as parameters to fill in for the Custom Connector when the end user will work on their Flows/Apps.
The info I’m choosing to fill is this – I’m giving a name to the parameter to indicate what info is required. The actual parameter name required by the Azure Function, in this case – it’s ‘code’ and since I need to pass the API key in Query string, I’ve selected Query instead of Header.
When you go to the next part, i.e. Definition, make sure you also give a Name to the Custom Connector already. Before your lose the info you’ve already entered. Make sure you also click on Create Connector

Once you click on Create connector, it’ll create it in a few moments.
Now, since you are aware of Triggers and Actions from using Power Automate – in this use case, my Custom Connector is designed to be an Action i.e. when called/used in Power Automate, it’ll simply perform the operation it’s designed to do.
Hence, I’m selecting an Action here.
When I select New Action from the left hand pane, it’ll open up information for me to fill out to describe the Action.
Now, since this will appear as a listed item in Actions in my Power Automate connector, I’m filling in this info (and we can check later how it appears).

Next, I’ll click on + Import from sample as it’ll give me a place to enter a sample for the request to call my hosted Azure Function.
Next, I’ll pass these values as I did in Postman to create the sample. Once done, I can click on Import.
When I import, I’ll the request parameters set in the Custom Connector based on the sample I entered.
Next, I’ll scroll down to ensure that all validations are perfect and I needn’t fix anything.
Next, I’ll skip AI Plugins step and also the Code step since I want to keep this example concise and to the scope of the hosted Azure Function only.

And this is skipped too –
Now, the final step is to Test the Custom Connector. The Editor will ask you to Update connector before you can Test. Then, in order to begin testing – you’ll need to first create a Connection using New Connection button as shown below.
When you click on New Connection, you’ll be taken to a new tab to enter the API key which you created as parameter in the initial setup of this Connector. See #7 above. Enter the API key you have which works for this hosted app and then click Create connection.
Next, in case the Connection doesn’t appear, click Refresh button once.
Once you refresh, you should see your Connection come up and selected.
Now, next step is to test the Custom Connector itself. Enter the values that you wish to test for and click Test operation.
You’ll see the test results based on what the hosted code is supposed to perform.
In my case, it was easy as it just greets the name entered.

And your Custom Connector is now ready to be used!

Consuming Custom Connector

Now, let’s see how you can use the Customer Connector in Power Automate in order to perform the operation in your Flows –

Once in Power Automate, look for the Custom tab in the Action selector.
Then, you can see the Action you defined in your Connector Definition steps above.
Since you need to authenticate using the API key you have, the create Connection step will ask you this info and you can give the name of the Connection.
Pass the value you want to pass as data.
Finally, you can just save and test the Flow itself and look for your Outputs.

And that’s how you can have a Custom Connector for your custom app/service your have created. I’ll soon write about other aspects of Custom Connector which I wasn’t able to cover in this blog.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

HTTP Trigger Azure Function Authorization Types simplified

July 14, 2024July 14, 2024 priyeshwagh777 Azure Functions, Microsoft Azure azure, cloud, power apps, Power Automate, Power Platform

Now, many of you must be wondering how the Authorization types for Azure Functions using HTTP Triggers work and where to look for information while using these different types. Hopefully, this post helps simplify each of those for you.

Now, when you create a new Azure Function from Visual Studio or from the Azure Portal, you’ll be asked about Authorization where you’ll find the selection to either be 1 of the below –

Anonymous
Function
Admin
System

Anonymous

This type of Authotization let’s you use the Azure Function without needing for any key and anyone with the URL alone can access it. Of course, this is not recommended for any production use –

Now, if you notice your Visual Studio, when you write your first Azure Function, it comes with pre-defined method ready for you to continue to write your own code. But right away, you’ll see that the Authorization method is pre-defined considering you must’ve selected Anonymous while starting the Project.
Also, since the Azure Function is understood to be Published already on the Azure Portal, you’ll see in the Function’s settings that the same has been reflected as well.
Now, if you test this using Postman, the code will be able to run directly just using the URL without any API key. Either you pass in the body – and you’ll get a 200 OK with the result that the Azure Function is supposed to result.

Or using query parameters – the result will be the same.

This simply explains Anonymous authorization. Without any check on who’s supposed to access the Azure Function.

Function

In this type of Authentication, only the Function and resources associated to it will be accessible. This needs the caller to have a key [or code] to be passed while calling Azure Function –

Let’s look at the code, and see that the type is not set to Function for Authorization.
And when you Publish the code, the same will be reflected in the Settings too.
And when you want to access the Azure Function from Postman, you’ll need the Function Keys defined in the Function Keys area of the Function itself – a Default Key is given already but you can choose to add your own keys and using any of them would do.
Now, here’s what the Key looks like when you click on Show [there’s a button on the far right to expose the key’s value]
Now, when you go to Postman, you need to can pass this as a query parameter –

Now, let’s look at the Admin Type of Authorization.

Admin

In this type of Authorization, you get access to Functions’ Runtime APIs. The way to use the Admin key is similar to the Function Keys, just that they are available from the Function App itself than the Function –

Now, when the Authorization is set to Admin
You’ll see this reflected in the portal once Published.
Now, in the Function App itself – you can navigate to the App keys under Functions [as of the portal’s layout in mid-2024]
You can expose to see this value and share it to the clients who are going to consume this Function App. They key required here is the _master
Now, you can test this using Postman

Remember, this type of Authorization is to be used when the calling client needs to also access Functions Runtime API.
Finally, Let’s look at the System type.

System

This type of key is managed by Function runtime and is used when the calling client when there’s a need for granular access to function runtime features.

Now, you can set this from the code and publish it.
And it’ll appear in the settings of the Function [In case when the Function wants to access granular function runtime features].
And this is present in the App keys area under System Keys section.
And when you test the same, they work just like any other key from the Function app when called.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Permanently Delete a User in Entra ID

December 31, 2023 priyeshwagh777 Microsoft Azure entra id user, permanently delete user

In case you are managing Users in Microsoft 365, a Deleted User still exists in Soft Delete state for 30 days.
Here’s how you can immediately delete the user permanently!
Please do this when you are entirely sure that you want to delete the User as this a permanent step and won’t get back the User once deleted.

Azure Admin Portal

Here’s how you can access the Azure Portal and then delete the User –

Unlike M365, go to Azure Portal (https://portal.azure.com/#home), then look for Entra ID
Then, look for Users.
In Users, go to Deleted Users.
There, you’ll find the Soft Deleted Users, select the User you want to delete and then click on Delete Permanently.
You’ll need to refresh the page after a few moments to see that the User is not gone.

Hope this is useful!

Here are some Power Automate posts you want to check out –

Thank you!

Power Platform self-service analytics Data Export to Data Lake [Preview] | Power Platform Admin Center

January 31, 2023 priyeshwagh777 Microsoft Azure, Power Platform, Power Platform Admin Center adls gen 2, data export to data lake, Power Platform Admin Center, power platform data export, power platform data export to data lake, self service analytics power platform

Now, you can also export the Analytics Data to Azure Data Lake in order to further extend the derive rich data analytics!
At the time of writing this post, this feature is in Preview (As you’ll also see from the screenshots below)

This is a great feature where you can extract this Data into Data Lake and then further enrich and derive rich Power BI reporting based on your use-case.

In case you are new to understanding Azure Data Lake and pricing, you can review this – https://azure.microsoft.com/en-gb/solutions/data-lake/?WT.mc_id=DX-MVP-5003911

Data Export (Preview)

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), here’s how you can setup Data Export –

Navigate to Data Export in Power Platform Admin Center given that you have appropriate rights –
Then, you’ll get to choose amongst the Power Apps or Power Automate data to be exported to Data Lake.
In this example, I’ll choose Power Automate. As I select Power Automate, you’ll see that Tenant-Level Analytics are required and hence, already considered as Yes. If not, you’ll need to Enable Tenant-Level Analytics while doing this step – Here’s another post on how to Enable and Use Tenant Level Analytics –
Now, In the next section you’ll need to choose the Subscription.
Further, select the Resource Group and eventually, the Storage Account as well.

And Storage Account is selected as well.
Once everything looks good, you can click on Create.
In a few moments, this will appear in Data Lake section of the Data Export. It will take up to 24 hours for the data to first start showing in Data Lake.
Once this is completed after about 24 hours, you’ll see the status of the Data Lake data package changed to connected.

Data Export to Data Lake

Let’s look at the Azure Storage Explorer to connect to our Data Lake and see the Power Platform data – In case you are looking to install Azure Storage Explorer, here’s a post – Microsoft Azure Storage Explorer | Getting Started

Once authenticated to the correct environment in Azure Storage Explorer, here’s what you would see in the ADLS Gen 2 (In case you want to create ADLS Gen 2 storage account, you can review this post – Create ADLS Gen 2 Storage Account for Azure Data Lake)
You’ll see powerplatform folder show up.
If you open this folder, since we had chosen Power Automate, it’s folder will be created.
And let’s go in Flows folder to see the data. You’ll find json files of the same. You can double click to open it and it’ll open in whatever editor you have installed.
In this case, I had VS Code, so here’s what the Flow data looks like –
Likewise, you can dig deeper in this data and use this further for your reporting!

Here’s Microsoft Learn Document on the same – https://learn.microsoft.com/en-us/power-platform/admin/self-service-analytics?WT.mc_id=DX-MVP-5003911

Here’s Microsoft Learn Docs for Tenant-Level Analytics – https://learn.microsoft.com/en-gb/power-platform/admin/tenant-level-analytics#how-do-i-enable-tenant-level-analytics?WT.mc_id=DX-MVP-5003911

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Create ADLS Gen 2 Storage Account for Azure Data Lake

January 29, 2023January 29, 2023 priyeshwagh777 Microsoft Azure adls gen 2, azure data lake, azure data lake gen 2 storage, azure storage account, data lake storage

Here’s how you can create an ADLS Gen 2 Storage for Azure Data Lake!

Resource Group and Storage Account

In case you don’t have a Resource Group already, create one and have all the new Resources including this Storage Account also in this new one.

I have a blank Resource Group called Jan 2023. It is blank and hence, I’ll start by creating Azure Storage in the same.
When in the Resource Group, look for + Create button and it’ll take you to the Marketplace to create Storage Account.
Once in Marketplace, search for “Storage Account” and you’ll see one by Microsoft as below. Click on Create.
Once you click on Create (it may expand and let you click on Storage Account action – redundant, but it is what it is)
Then, enter all the details, make sure the correct Resource Group is selected and give a name (no special characters and it has to be in small caps) to the Storage Account.
Once I click on Next: Advanced, look for Data Lake Gen 2 area in Advanced tab (which would be disabled by default).
Click on Enable Hierarchical namespace to make it Gen 2
Make sure you have checked Enable hierarchical namespace option.
Finally, review all the options you may have made. I’ve not changed anything else to keep it within the context of this blog.
Then, once the button is enabled.
On the final page, it might take a few moments for the Create button to appear. Once everything looks good, click on Create.
It’ll start deployment as any other resource in Azure and you’ll know once it’s completed.
And this will complete in a few moments.
Once this is completed, you can also check in Azure Storage Explorer
Below is how it’ll appear in the Azure Storage Explorer.
In case you are looking to setup and use Azure Storage Explorer, you can check this post – Microsoft Azure Storage Explorer | Getting Started

And your Gen 2 Storage for Data Lake is created.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Microsoft Azure Storage Explorer | Getting Started

January 29, 2023 priyeshwagh777 Microsoft Azure azure storage explorer, install microsoft storage explorer, microsoft azure storage explorer, storage explorer

If you are wondering how to get and setup the Microsoft Azure Storage Explorer – Here’s this post!

Azure Storage Explorer

Here’s how you can download and setup Microsoft Azure Storage Explorer.

Search For Azure Storage Explorer and you’ll see something as below –
Once you open the azure.microsoft.com link, you’ll see the below –
Drop down to select Windows. And the Setup will will be prompted to save on your browser (or directly download based on your browser settings)
And it’ll appear that it has been downloaded to your machine.
Now, click on the Setup and let it start. Accept the Terms if everything looks OK to you, then click on Install
It’ll then ask you where to setup and what it should call on the system. Standard stuff.
Then, installation will begin.
Then, open it up when finished.
Now, this will come up. You are now ready to Sign-In!

Sign In with Azure in Microsoft Storage Explorer

Now, picking up from the step above, here’s how you sign in –

Click on the Sign In with Azure if that’s your case unless you are trying other options in this wizard.
If your Azure is usual one to login, can you simply click on Azure and click Next.
Then, you’ll be asked to authenticate. Enter your credentials and authenticate like you would for any Microsoft Account.
Once successful, you’ll see this and you can close the window.
Now, if you open the App, it’ll detect your Azure Subscription if you have one.
If it looks correct, you can simply click on Open Explorer.
Once opened, you can expand on the Subscription and see all your Storage Accounts.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Setting up Billing Policy for Dataverse Environments in Power Platform for Azure Pay-As-You-Go plan | Microsoft Azure

October 31, 2022October 31, 2022 priyeshwagh777 Microsoft Azure, Microsoft PowerApps, Power Platform Admin Center Dataverse, Microsoft Azure, power apps, power platform billing policy, power platform pay as you go

Pay-as-you-go has been recently announced with Azure and I too wanted to explore this topic myself on my trials Dataverse/D365 Sales environment as well as my Microsoft Azure trial subscription which I started.

Disclaimer: Please note that I’m exploring this topic and sharing as I go on. Hence, I’ll continue to write further topics as I proceed. Please try on your Dataverse trial & Microsoft Azure trial subscription to identify / estimate the costs your actual implementation will incur.

I also recommend going through the below Microsoft Learn Pages for detailed information on pricing and meters of the Pay-as-you-go model –

Detailed Microsoft Docs for Pay-as-you-go: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-overview?WT.mc_id=DX-MVP-5003911

Power Apps Pricing: https ://powerapps.microsoft.com/en-us/pricing/

Pay-as-you-go Meters: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-meters?tabs=image?WT.mc_id=DX-MVP-5003911

Let’s see how we can get started!

Setting up Billing Policy

Here’s how you create Billing Policy in Power Platform –

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), you can see Policies section. If you expand the same, you can see Billing Policies.
Here, you can start by creating a new Billing Policy
You can give it an appropriate name. And it doesn’t allow you to have spaces.
Next, you’ll be asked to select the Subscription you wan to assign the Billing Policy under.
Notice the error below. My Free Trial Azure Subscription doesn’t have a Resource Group created yet. Hence, this need to be present.
Since at this point, I don’t have a Resource Group under the Azure Subscription I selected, I need to go to Azure Portal (https://portal.azure.com/), search for Resource Groups
Since you might not have any Resource Group right away, you can create one.
I’ll just give it a name which I can identify with.
I’ll validate and Create the same in Azure.
Resource Group will be created here.
Now, when I come back to Power Platform, if I reselect the Azure Subscription, I’ll now see that the Resource Group I created is showing up.
I’ll select the same and select United States as the Region.
And click on Next.
In the next steps, I can select which all Environments should be included in the Policy. Then, I can click on + Add to policy.
You can see the Added to policy tab now showing your environment. Once you are satisfied with the selection, you can click on Next.
Final step is to now Review and confirm the policy you are creating.
It’ll take a moment to start provisioning. Then, you’ll see the status as Provisioning.
Once completed, the status will show as Enabled.
Now, when you go back to Azure Portal and open the Resource Group, you’ll find a Deployment show up
Open it up and you’ll see a Deployment created.
And if you open the Deployment, you can see the DataverseBilling which we had set up in Power Platform.
And this point, you are now setup with using Pay-As-you-go plan for your Dataverse environment(s).

Note: Further, I’ll write follow up posts as I explore Pay-as-you-go scenarios and experience myself.

Hope this helps!

Here are some Power Automate posts you want to check out –

Thank you!

Create Azure DevOps Organization in your tenant

October 26, 2022 priyeshwagh777 Microsoft Azure azure devops, create org in azure devops, sign up on azure devops

Here’s how you can create Org in Azure DevOps!

Login to DevOps

here’s how you can search for Azure Dev Ops as below –

You can use this URL [https://azure.microsoft.com/en-us/products/devops/] which will take you to the Azure DevOps Home Page –
You’ll see the Sign in to Azure DevOps button as shown below
Once you click on Sign in, you’ll see this screen where you need to enter the name of the Org (which is already pre-populated) –
So, I’ll just click on Continue.
Next, you’ll need to agree to terms.
Then, you’ll be asked to provide a name of the organization for the DevOps, so I’ll enter here as an example based on what my trial Org is named.
Also, you can change where the server location. Finally, enter Captcha and click Continue.
Once I click Continue, next, I’ll see this where it will create the Organization for me.
Once this is completed, I’ll be asked to create the first Project right away –
You can leave it here if you don’t want to create a Project right away. Your DevOps organization has been set up though.
But, as an example – I’ll create my first Project just to show you. So, I’ll enter a sample project and click on ” + Create project“
And once this is created, here’s how it will look in the list of projects. You can open it up and see what all is available –
And this is how the Project itself has by default.

Create Org from Azure Portal

Here’s an alternate way from the Azure Portal (https://portal.azure.com/#home) to create your DevOps organization in your tenant –

Search for DevOps in Azure Portal and you’ll see the below option –
And when you go to Azure DevOps organizations, you’ll see the below homepage.
You can then spot My DevOps organization button to show which all DevOps orgs have been created.
If you don’t have any organizations at this point, you’ll be asked to create one just as in the first method shown above –
If you already have at least 1 Org created, you’ll be show the list of organizations in the DevOps which have been created-

Here are some Power Automate posts you want to check out –

Thank you!

Skip requirement to enter authentication method in M365 Login | Turn off Security Defaults

May 11, 2022 priyeshwagh777 Microsoft Azure microsoft 365 administration, security defaults, two-factor authentication

If you newly created a an M365 tenant, this is what you’ll be forced to by to enter authentication methods in this Security Defaults feature –

In most cases, even clicking on Skip for now option doesn’t help and I’m forced to enter an alternate authentication method.
Ideally, for Production purposes, you should keep this turned on. Only if you are on a trial and the tenant you are working on is for learning purposes, it is OK to turn this off.

Turn Off Security Defaults in Azure Portal

Here’s how you can turn off the Security Defaults requirement from the Azure Portal –

Navigate to Azure Portal (https://portal.azure.com)
Again, you’ll see this message so you can choose to skip this since we want to disable the Security Defaults.
Then, go to Azure Active Directory
Once in Azure Active Directory, look for the Settings in the left hand pane.
In Properties, at the bottom you’ll see the Manage Security defaults button.
It would be turned on by default (Yes) which you’ll need to switch to No.
Once you switch to No, you’ll need to select either of the below reasons as to why you are switching it off. I just entered N/A in the Others reason, your reason could be different.
Once you Save it, that’s all. Now you can just close the Window and try to Login again.

Logging in without Security Defaults

When the Security Defaults is turned off, you can see that the login screen will no longer ask you to enter an authentication method –

When you enter password.
And when you sign in, you’re no longer asked to enter a method for authentication and you’re already logged in past that step.

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

Thank you!!

Create Application Users for Dynamics 365 environment | Power Platform Admin Center

March 30, 2022February 7, 2024 priyeshwagh777 Azure Functions, Microsoft Azure, Power Platform Admin Center application users in crm, application users in dynamics 365 crm, Power Platform Admin Center, ppac application users

Here’s how you now set up Application Users in Dynamics 365 CRM from the Power Platform Admin Center instead from the Classic UI and let’s see how the process is eased.

Classic UI

Previously, you used to see Application Users view in the Dynamics 365 CRM under Settings > Security > Users.

But it’s not longer available. Instead, you now go to the Power Platform Admin Center.

Register App in Power Platform Admin Center [PPAC]

Now, once you are in the Power Platform Admin Center, you can go to the Environment section –

First, let’s say this is your App in your Azure’s Active Directory in the App Registrations. And now you want to create an Application User in Dynamics CRM for this App.
Now, you can go to the PPAC (https://admin.powerplatform.microsoft.com/) and in Environments, look for your D365 CRM/Dataverse environment.
In Settings, you’ll see Users, expand the same and you’ll see Application Users which is now it’s own separate option.
Now, you’ll see the Registered Apps I have already and you can add from the “+ New App User” button above.
Now, select the + Add an app button
And you’ll see the complete list of all the Apps that are in your Azure’s Active Directory. Select the one your just created and click Add.
And then finally click Create once you Add the App you want to create Application User for.
And now, you’ll see the App added as an Application User for your environment.
Now, you also need to provide Security Roles based on the requirement. Select the App User, and click on Edit security roles once available.
In my case, I’m giving 3 Roles which I need to give and click Save.
Now, I’ll also see how many Roles have been given to the App User.

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

Thank you!!

D365 Demystified

A closer look at Microsoft Dynamics 365.

Microsoft Azure

Create a Custom Connector For Power Automate & Power Apps

Use Case

Create Custom Connector in Power Apps / Power Automate

Consuming Custom Connector

Like this:

Permanently Delete a User in Entra ID

Azure Admin Portal

Like this:

Power Platform self-service analytics Data Export to Data Lake [Preview] | Power Platform Admin Center

Data Export (Preview)

Data Export to Data Lake

Like this:

Create ADLS Gen 2 Storage Account for Azure Data Lake

Resource Group and Storage Account

Like this:

Microsoft Azure Storage Explorer | Getting Started

Azure Storage Explorer

Sign In with Azure in Microsoft Storage Explorer

Like this:

Setting up Billing Policy for Dataverse Environments in Power Platform for Azure Pay-As-You-Go plan | Microsoft Azure

Setting up Billing Policy

Like this:

Skip requirement to enter authentication method in M365 Login | Turn off Security Defaults

Turn Off Security Defaults in Azure Portal

Logging in without Security Defaults

Like this:

Create Application Users for Dynamics 365 environment | Power Platform Admin Center

Classic UI

Register App in Power Platform Admin Center [PPAC]

Like this:

Use Case

Create Custom Connector in Power Apps / Power Automate

Consuming Custom Connector

Share this:

Like this:

Anonymous

Function

Admin

System

Share this:

Like this:

Azure Admin Portal

Share this:

Like this:

Data Export (Preview)

Data Export to Data Lake

Share this:

Like this:

Resource Group and Storage Account

Share this:

Like this:

Azure Storage Explorer

Sign In with Azure in Microsoft Storage Explorer

Share this:

Like this:

Setting up Billing Policy

Share this:

Like this:

Login to DevOps

Create Org from Azure Portal

Share this:

Like this:

Turn Off Security Defaults in Azure Portal

Logging in without Security Defaults

Share this:

Like this:

Classic UI

Register App in Power Platform Admin Center [PPAC]

Share this:

Like this: