Skip to content

Add Microsoft.Communication to the All() resource provider list#32048

Closed
baranyaimate wants to merge 2 commits intohashicorp:mainfrom
baranyaimate:feature/add-microsoft-communication-resource-provider
Closed

Add Microsoft.Communication to the All() resource provider list#32048
baranyaimate wants to merge 2 commits intohashicorp:mainfrom
baranyaimate:feature/add-microsoft-communication-resource-provider

Conversation

@baranyaimate
Copy link
Copy Markdown
Contributor

Community Note

  • Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

Added Microsoft.Communication to the All() resource provider list.

PR Checklist

  • I have followed the guidelines in our Contributing Documentation.
  • I have checked to ensure there aren't other open Pull Requests for the same update/change.
  • I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
  • I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
  • I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
    For example: “resource_name_here - description of change e.g. adding property new_property_name_here

Changes to existing Resource / Data Source

  • I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
  • I have written new tests for my resource or datasource changes & updated any relevant documentation.
  • I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
  • (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

  • My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

This is a (please select all that apply):

  • Bug Fix
  • New Feature (ie adding a service, resource, or data source)
  • Enhancement
  • Breaking Change

Related Issue(s)

Fixes #31594

AI Assistance Disclosure

  • AI Assisted - This contribution was made by, or with the assistance of, AI/LLMs

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

@baranyaimate baranyaimate requested review from a team, WodansSon and magodo as code owners March 26, 2026 17:14
@baranyaimate baranyaimate changed the title Added Microsoft.Communication to the All() resource provider list Add Microsoft.Communication to the All() resource provider list Mar 26, 2026
@sreallymatt
Copy link
Copy Markdown
Collaborator

Hi @baranyaimate - we no longer recommend using the resource_provider_registrations property, and as such, we are no longer adding additional RPs to the predefined sets.

Instead, the resource_providers_to_register field can be used.

@baranyaimate baranyaimate deleted the feature/add-microsoft-communication-resource-provider branch March 26, 2026 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Microsoft.Communication in resource_provider_registrations

2 participants