{"id":19504919,"url":"https://github.com/tools4everbv/helloid-conn-prov-target-azure-setmanager","last_synced_at":"2026-05-15T04:35:19.050Z","repository":{"id":113209730,"uuid":"477831016","full_name":"Tools4everBV/HelloID-Conn-Prov-Target-Azure-SetManager","owner":"Tools4everBV","description":"Azure Active Directory - Target (set manager)","archived":false,"fork":false,"pushed_at":"2024-01-10T11:21:42.000Z","size":38,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":6,"default_branch":"main","last_synced_at":"2025-01-08T10:45:40.788Z","etag":null,"topics":["dir","itm","provisioning","target"],"latest_commit_sha":null,"homepage":"","language":"PowerShell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Tools4everBV.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-04-04T18:46:06.000Z","updated_at":"2023-05-11T11:44:35.000Z","dependencies_parsed_at":null,"dependency_job_id":"60678ada-fcba-4e4e-a69d-1dff5cd84d62","html_url":"https://github.com/Tools4everBV/HelloID-Conn-Prov-Target-Azure-SetManager","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-Prov-Target-Azure-SetManager","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-Prov-Target-Azure-SetManager/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-Prov-Target-Azure-SetManager/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-Prov-Target-Azure-SetManager/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Tools4everBV","download_url":"https://codeload.github.com/Tools4everBV/HelloID-Conn-Prov-Target-Azure-SetManager/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240754367,"owners_count":19852189,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["dir","itm","provisioning","target"],"created_at":"2024-11-10T22:27:41.780Z","updated_at":"2026-05-15T04:35:14.016Z","avatar_url":"https://github.com/Tools4everBV.png","language":"PowerShell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# HelloID-Conn-Prov-Target-Azure-SetManager\n\n| :information_source: Information |\n|:---------------------------|\n| This repository contains the connector and configuration code only. The implementer is responsible to acquire the connection details such as username, password, certificate, etc. You might even need to sign a contract or agreement with the supplier before implementing this connector. Please contact the client's application manager to coordinate the connector requirements.       |\n\u003cbr /\u003e\n\u003cp align=\"center\"\u003e\n  \u003cimg src=\"https://www.tools4ever.nl/connector-logos/azureactivedirectory-logo.png\"\u003e\n\u003c/p\u003e\n\u003c!-- TABLE OF CONTENTS --\u003e\n## Table of Contents\n* [Introduction](#introduction)\n* [Getting the Azure AD graph API access](#getting-the-azure-ad-graph-api-access)\n  * [Application Registration](#application-registration)\n  * [Configuring App Permissions](#configuring-app-permissions)\n  * [Authentication and Authorization](#authentication-and-authorization)\n\n## Introduction\nThe interface to communicate with Microsoft Azure AD is through the Microsoft Graph API. GetConnectors are based on a pre-defined 'data collection', which is an existing view based on the data inside the Profit database.\n\nFor this connector we correlate to an existing accoutn then set the manager. This is helpful if you have multiple source systems and need to cross reference by ID\n\n\u003c!-- GETTING STARTED --\u003e\n## Getting the Azure AD graph API access\n\nBy using this connector you will have the ability to manage Azure AD Guest accounts.\n\n### Application Registration\nThe first step to connect to Graph API and make requests, is to register a new \u003cb\u003eAzure Active Directory Application\u003c/b\u003e. The application is used to connect to the API and to manage permissions.\n\n* Navigate to \u003cb\u003eApp Registrations\u003c/b\u003e in Azure, and select “New Registration” (\u003cb\u003eAzure Portal \u003e Azure Active Directory \u003e App Registration \u003e New Application Registration\u003c/b\u003e).\n* Next, give the application a name. In this example we are using “\u003cb\u003eHelloID PowerShell\u003c/b\u003e” as application name.\n* Specify who can use this application (\u003cb\u003eAccounts in this organizational directory only\u003c/b\u003e).\n* Specify the Redirect URI. You can enter any url as a redirect URI value. In this example we used http://localhost because it doesn't have to resolve.\n* Click the “\u003cb\u003eRegister\u003c/b\u003e” button to finally create your new application.\n\nSome key items regarding the application are the Application ID (which is the Client ID), the Directory ID (which is the Tenant ID) and Client Secret.\n\n### Configuring App Permissions\nThe [Microsoft Graph documentation](https://docs.microsoft.com/en-us/graph) provides details on which permission are required for each permission type.\n\nTo assign your application the right permissions, navigate to \u003cb\u003eAzure Portal \u003e Azure Active Directory \u003eApp Registrations\u003c/b\u003e.\nSelect the application we created before, and select “\u003cb\u003eAPI Permissions\u003c/b\u003e” or “\u003cb\u003eView API Permissions\u003c/b\u003e”.\nTo assign a new permission to your application, click the “\u003cb\u003eAdd a permission\u003c/b\u003e” button.\nFrom the “\u003cb\u003eRequest API Permissions\u003c/b\u003e” screen click “\u003cb\u003eMicrosoft Graph\u003c/b\u003e”.\nFor this connector the following permissions are used as \u003cb\u003eApplication permissions\u003c/b\u003e:\n*\tRead and Write all user’s full profiles by using \u003cb\u003e\u003ci\u003eUser.ReadWrite.All\u003c/i\u003e\u003c/b\u003e\n*\tRead and Write all groups in an organization’s directory by using \u003cb\u003e\u003ci\u003eGroup.ReadWrite.All\u003c/i\u003e\u003c/b\u003e\n*\tRead and Write data to an organization’s directory by using \u003cb\u003e\u003ci\u003eDirectory.ReadWrite.All\u003c/i\u003e\u003c/b\u003e\n\nSome high-privilege permissions can be set to admin-restricted and require an administrators consent to be granted.\n\nTo grant admin consent to our application press the “\u003cb\u003eGrant admin consent for TENANT\u003c/b\u003e” button.\n\n### Authentication and Authorization\nThere are multiple ways to authenticate to the Graph API with each has its own pros and cons, in this example we are using the Authorization Code grant type.\n\n*\tFirst we need to get the \u003cb\u003eClient ID\u003c/b\u003e, go to the \u003cb\u003eAzure Portal \u003e Azure Active Directory \u003e App Registrations\u003c/b\u003e.\n*\tSelect your application and copy the Application (client) ID value.\n*\tAfter we have the Client ID we also have to create a \u003cb\u003eClient Secret\u003c/b\u003e.\n*\tFrom the Azure Portal, go to \u003cb\u003eAzure Active Directory \u003e App Registrations\u003c/b\u003e.\n*\tSelect the application we have created before, and select \"\u003cb\u003eCertificates and Secrets\u003c/b\u003e\". \n*\tUnder “Client Secrets” click on the “\u003cb\u003eNew Client Secret\u003c/b\u003e” button to create a new secret.\n*\tProvide a logical name for your secret in the Description field, and select the expiration date for your secret.\n*\tIt's IMPORTANT to copy the newly generated client secret, because you cannot see the value anymore after you close the page.\n*\tAt least we need to get is the \u003cb\u003eTenant ID\u003c/b\u003e. This can be found in the Azure Portal by going to \u003cb\u003eAzure Active Directory \u003e Custom Domain Names\u003c/b\u003e, and then finding the .onmicrosoft.com domain.\n\n# HelloID Docs\nThe official HelloID documentation can be found at: https://docs.helloid.com/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftools4everbv%2Fhelloid-conn-prov-target-azure-setmanager","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftools4everbv%2Fhelloid-conn-prov-target-azure-setmanager","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftools4everbv%2Fhelloid-conn-prov-target-azure-setmanager/lists"}