{"id":19505011,"url":"https://github.com/tools4everbv/helloid-conn-sa-full-teams-removechannel","last_synced_at":"2025-06-28T05:36:12.686Z","repository":{"id":113214329,"uuid":"318777850","full_name":"Tools4everBV/HelloID-Conn-SA-Full-Teams-RemoveChannel","owner":"Tools4everBV","description":"Microsoft Teams - Team remove channel","archived":false,"fork":false,"pushed_at":"2024-09-01T15:10:30.000Z","size":31,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":5,"default_branch":"main","last_synced_at":"2025-01-08T10:45:45.780Z","etag":null,"topics":["delegated-form","import","microsoft-teams","powershell","service-automation"],"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":"2020-12-05T12:03:50.000Z","updated_at":"2023-09-08T14:05:12.000Z","dependencies_parsed_at":null,"dependency_job_id":"2b870c87-ff84-44ed-b50c-d83b0667d8e8","html_url":"https://github.com/Tools4everBV/HelloID-Conn-SA-Full-Teams-RemoveChannel","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-SA-Full-Teams-RemoveChannel","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-SA-Full-Teams-RemoveChannel/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-SA-Full-Teams-RemoveChannel/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Tools4everBV%2FHelloID-Conn-SA-Full-Teams-RemoveChannel/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Tools4everBV","download_url":"https://codeload.github.com/Tools4everBV/HelloID-Conn-SA-Full-Teams-RemoveChannel/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":["delegated-form","import","microsoft-teams","powershell","service-automation"],"created_at":"2024-11-10T22:28:02.641Z","updated_at":"2025-02-25T22:13:51.110Z","avatar_url":"https://github.com/Tools4everBV.png","language":"PowerShell","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003c!-- Description --\u003e\n## Description\nThis HelloID Service Automation Delegated Form can delete a Channel of a Microsoft Teams Team\n\n## Versioning\n| Version | Description | Date |\n| - | - | - |\n| 1.2.0   | Updated to Graph API with audit-logging | 2022/10/18  |\n| 1.1.0   | Updated with code for SA agent | 2022/03/14  |\n| 1.0.1   | Added version number and updated all-in-one script | 2021/12/13  |\n| 1.0.0   | Initial release | 2020/12/05  |\n\n\u003c!-- TABLE OF CONTENTS --\u003e\n## Table of Contents\n- [Description](#description)\n- [Versioning](#versioning)\n- [Requirements](#requirements)\n- [Table of Contents](#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- [All-in-one PowerShell setup script](#all-in-one-powershell-setup-script)\n  - [Getting started](#getting-started)\n- [Post-setup configuration](#post-setup-configuration)\n- [Manual resources](#manual-resources)\n- [Getting help](#getting-help)\n- [HelloID Docs](#helloid-docs)\n\n\n## Introduction\nThe interface to communicate with Microsoft Azure AD is through the Microsoft Graph API.\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 enable or disable an Azure AD User.\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*\tAllows the app to read the full set of profile properties, reports, and managers of other users in your organization, on your behalf by using \u003cb\u003e\u003ci\u003eUser.Read.All\u003c/i\u003e\u003c/b\u003e\n*\tRead all channel names, channel descriptions, and channel settings, on your behalf by using \u003cb\u003e\u003ci\u003eChannelSettings.Read.All\u003c/i\u003e\u003c/b\u003e\n*\tCreate channels in any team, on your behalf by using \u003cb\u003e\u003ci\u003eChannel.Create\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## All-in-one PowerShell setup script\nThe PowerShell script \"createform.ps1\" contains a complete PowerShell script using the HelloID API to create the complete Form including user defined variables, tasks and data sources.\n\n_Please note that this script asumes none of the required resources do exists within HelloID. The script does not contain versioning or source control_\n\n### Getting started\nPlease follow the documentation steps on [HelloID Docs](https://docs.helloid.com/hc/en-us/articles/360017556559-Service-automation-GitHub-resources) in order to setup and run the All-in one Powershell Script in your own environment.\n\n## Post-setup configuration\nAfter the all-in-one PowerShell script has run and created all the required resources. The following items need to be configured according to your own environment\n 1. Update the following [user defined variables](https://docs.helloid.com/hc/en-us/articles/360014169933-How-to-Create-and-Manage-User-Defined-Variables)\n\u003ctable\u003e\n  \u003ctr\u003e\u003ctd\u003e\u003cstrong\u003eVariable name\u003c/strong\u003e\u003c/td\u003e\u003ctd\u003e\u003cstrong\u003eExample value\u003c/strong\u003e\u003c/td\u003e\u003ctd\u003e\u003cstrong\u003eDescription\u003c/strong\u003e\u003c/td\u003e\u003c/tr\u003e\n  \u003ctr\u003e\u003ctd\u003eAADtenantID\u003c/td\u003e\u003ctd\u003eAzure AD Tenant Id\u003c/td\u003e\u003ctd\u003eId of the Azure tenant\u003c/td\u003e\u003c/tr\u003e\n  \u003ctr\u003e\u003ctd\u003eAADAppId\u003c/td\u003e\u003ctd\u003eAzure AD App Id\u003c/td\u003e\u003ctd\u003eId of the Azure app\u003c/td\u003e\u003c/tr\u003e\n  \u003ctr\u003e\u003ctd\u003eAADAppSecret\u003c/td\u003e\u003ctd\u003eAzure AD App Secret\u003c/td\u003e\u003ctd\u003eSecreat of the Azure app\u003c/td\u003e\u003c/tr\u003e\n\u003c/table\u003e\n\n## Manual resources\nThis Delegated Form uses the following resources in order to run\n\n### Powershell data source '[powershell-datasource]_Teams-generate-table-wildcard'\n\n### Powershell data source '[powershell-datasource]_Teams-get-team-channels'\n\n### Delegated form task '[task]_Teams - Remove Team Channel'\n\n## Getting help\n_If you need help, feel free to ask questions on our [forum](https://forum.helloid.com/forum/helloid-connectors/service-automation/652-helloid-sa-microsoft-teams-remove-channel)_\n\n## HelloID Docs\nThe official HelloID documentation can be found at: https://docs.helloid.com/","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftools4everbv%2Fhelloid-conn-sa-full-teams-removechannel","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftools4everbv%2Fhelloid-conn-sa-full-teams-removechannel","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftools4everbv%2Fhelloid-conn-sa-full-teams-removechannel/lists"}