![myatt app enable data myatt app enable data](https://www.iclarified.com/images/news/19558/69153/69153.jpg)
Go to and click on gear icon on the top right, and select “Custom Connectors”. Step 3: Add This Registered App As A Custom Connector In Your PowerApps Environmentġ. On clicking this url, your Active Directory Tenant Admin will get the prompt to grant permission. In the url below, put the client id (or application id) you noted while registering the app in the active directory. Send the following url to the Active Directory Admin (it is typically someone from your IT Department). Go to settings -> Required Permissions, and click on Grant Permissions button at the top: There are 2 ways to do this:Īsk the admin to the Azure portal, go to Azure Active Directory -> App Registrations -> and select the app you registered in the previous step. This step can be done only by the admin of the active directory. Step 2: Grant The Permissions Requested In The Previous Step (An Active Directory Admin Needs To Do This) Under “Delegated Permissions”, check following ones: On the next screen, select Microsoft Graph:ġ3. In the Required Permissions, click on Add and then Select an API:ġ1. Go back to Settings, click on Required Permissionsġ0. (Note- very important to note down this secret in this step because you won’t be able to see this key if you come back to this screen later. You’ll need this key secret in later step while registering this API as custom API in PowerApps. Enter a description for the key, choose the expiry period, and hit Save. I’ll go in greater details about that error at a later step (where you register this as custom connector in PowerApps environment).Ĩ. If you get error, you’ll have to come back and add your location specific url. Note- This url may not work for non US locations. From Settings, click on Reply URLs, add following url and hit save: After noting down the application id, click “Settings” menu at the top.Ħ. Note down the application id (it’ll be used as Client Id in the later step of adding this API as custom connector in PowerApps environment). Once it is created, select this newly created app. Name: Any Name that you want to use ( I used “GraphAPIDemo”)ĥ. For Registering a New App, use following values: Select Azure Active Directory -> App RegistrationĤ. If you have more than one Azure Active Directory tenant, make sure you’re logged into the correct directory by looking at your username in the upper-right corner.Ģ. These steps are similar to the steps documented in this example of custom api.ġ. Step 1: Register An App In The Azure Active Directory and Request Permission To Use The Right Graph API(s)
![myatt app enable data myatt app enable data](https://www.att.com/devicehowtomedia/image/iphone8/ios15/9006183_01.jpg)
MYATT APP ENABLE DATA HOW TO
If there is enough interest, I’ll do another blog post showing how to use the other graph api. You can use the concept outlined in this blog to make use of this other API (after finding group id from the graph explorer).
![myatt app enable data myatt app enable data](https://cdn.idropnews.com/wp-content/uploads/2018/08/23111037/ios8-icloud-backup-enable.jpg)
However you’ll need to know group id (you can’t use group name for using that API). There are other Graph APIs for finding nested group membership too. For this blog, we are keeping it simple by just checking for direct membership. So, it’ll miss out the group membership through nested group membership. Graph API we are using here, lists the groups that the user is direct member of.I find Graph Explorer very handy to explore what’s out there and even test out the output of the specific APIs before using this in my own code. If you never used Microsoft Graph before, I strongly recommend that you checkout their documentation and graph explorer.Step 4: Use the custom connector in your PowerApps app Step 3: Add this app as a custom connector in PowerApps environment Step 2: Grant Permission requested above (An Active Directory Admin needs to do this)
![myatt app enable data myatt app enable data](https://i.redd.it/i70clbyltqr21.jpg)
Step 1: Register an app in the Azure Active Directory and request permission to use the right Graph API(s) After getting the list of groups through this custom connector in PowerApps, we can easily check if the user belongs to a particular group and accordingly set the visibility of certain controls or screens. We’ll use custom connector feature of PowerApps to connect to Microsoft Graph API for listing the Active Directory Groups that the user belongs to*. In this blog post, I’ll show you how you can find out the Active Directory group membership of the signed in user and accordingly make decision to show/ hide certain features. For example, make Admin screen available only to the users who belong to an Active Directory Group “Administrators” or make management views available only to the users belonging to the Active Directory Group “Managers” (as shown in the picture below). In other words, how do I make certain features or screens of my app available only to the authorized people in my organization. A very common question our customers ask is, how do I implement role based access control in my app.