appservice: allow importing function app hybrid connections on elasti…

[jhern61]

azurerm_function_app_hybrid_connection - allow importing on Elastic plans (Fixes #31131)

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

This PR fixes a bug where importing an azurerm_function_app_hybrid_connection resource would fail if the Function App was running on an Elastic Premium plan (EP1, EP2, EP3).

Previously, the CustomImporter logic incorrectly treated Elastic plans as unsupported for Hybrid Connections. However, Microsoft documentation confirms that Hybrid Connections are available in Basic, Standard, Premium, and Isolated SKUs, which includes Elastic Premium.

This change removes the explicit check that blocked Elastic plans during import.

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)

Verified the fix by reviewing the official Microsoft documentation which states Elastic plans are supported. The change strictly removes an artificial blocker in the import logic.

Change Log

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

• azurerm_function_app_hybrid_connection - allow importing on Elastic plans (Fixes function_app_hybrid_connection_resource doesn't allow import when app service plan is Elastic, but works on creation #31131)

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 #31131

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.

None.

[sreallymatt]

Thanks @jhern61 LGTM ✅

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.