<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> Expose `inherit_from_id` attribute as a parameter in Integrations PUT API for Microsoft Teams: [Create/Edit Microsoft Teams integration API](https://docs.gitlab.com/ee/api/integrations.html#createedit-microsoft-teams-integration), so it can be updated. #### Customer use case When there is already a Microsoft Teams configuration on the group level, configuring a new Microsoft Teams integration at a project level will **Use default settings**. The customer wishes to manage the project settings via API for the integration to **Use custom settings** (`inherit_from_id` = nil). {width=50%} Excerpt from them: > we’re setting up all project settings via the API automatically based on a YAML configuration. When configuring this integration, it’s currently not working with the API, when there is already a configuration on group level. So our automatic approach is broken. ### Current workaround Use Rails console to set `inherit_from_id` as nil. ### Technical details To enable custom settings via API we have to upsert the `API::Helpers::IntegrationsHelpers` module. E.g. into the `'microsoft-teams'` we could add: ```ruby { required: false, name: :inherit_from_id, type: String, desc: 'The ID of ancestor' }, ``` with the change above, we will be able to set `inherit_from_id` value to `nil`, and update the rest of attributes. ### Documentation Documentation for this change needs to be added. <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->