You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
Description
Currently the azurerm_api_management_logger resource supports instrumentation_key via the application_insights block. As per Microsoft , this will no longer be supported come March 2025, and connection strings are needed instead. This is not supported in azurerm_api_management_logger and therefore needs to be added.
Is there an existing issue for this?
Community Note
Description
Currently the azurerm_api_management_logger resource supports instrumentation_key via the application_insights block. As per Microsoft , this will no longer be supported come March 2025, and connection strings are needed instead. This is not supported in azurerm_api_management_logger and therefore needs to be added.
New or Affected Resource(s)/Data Source(s)
azurerm_api_management_logger
Potential Terraform Configuration
References
https://azure.microsoft.com/en-gb/updates/technical-support-for-instrumentation-key-based-global-ingestion-in-application-insights-will-end-on-31-march-2025/
The text was updated successfully, but these errors were encountered: