Closed wgkesler closed 7 months ago
@wgkesler Thanks for your feedback! We will investigate and update as appropriate.
Thank you for reaching out to us! We appreciate your interest in improving our documentation.
We have been made aware of a benign ApplicationId
key-value pair occasionally appearing in connection strings. The exact circumstances under which this occurs is not yet understood. Our product group is investigating, and we will update the documentation as soon as we have more information.
As GitHub issues are coming to a close in favor of a new feedback mechanism (https://aka.ms/ContentUserFeedback), we have moved this feedback to an internal work item for tracking: https://dev.azure.com/msft-skilling/Content/_workitems/edit/238763
Our support team is available to assist you if this is a pressing question or problem that need to be resolved immediately. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/ #please-close
@AaronMaxwell Is there any news related ApplicationId key-value appearing in Connection String of Application Insights?
We just ran into this. It produces some nasty side effects, since there are some Terraform resources that need to be re-created if the connection string changes. All of a sudden this new proparty has appeared in our connection strings and is causing much confusion.
@saarivirtajCGI Exactly, that is the reason why I reported that issue - the consequences of the change of the connection string are huge, especially when using infrastructure as code approach and when there is no information in documentation.
@AaronMaxwell since you closed this one and moved to your internal backlog, could you tell us what is the status and the estimated time to resolve that issue?
@AaronMaxwell: ping...
New property ApplicationId is missing in Connection String syntax details.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.