-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implements fic credential #44108
Implements fic credential #44108
Conversation
/azp run net - Azure.Communication.SMS - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dinazavyr: Please add context to the description explaining the problem that you're attempting to solve and the scenarios that it applies to. Please also help us understand whether or not you've been working with a member of the Azure SDK team to advise on this submission.
Since this looks to be applicable to Communication.SMS, can you help us understand why you believe this change should be made in Azure.Core versus being applied locally in the Communication.SMS library?
/azp run net - Azure.Communication.SMS - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run net - Azure.Communication.SMS - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Given that we do not intend to move forward with this change in the Core framework at this time and inquires have gone unanswered, closing this out. If this is functionality necessary for the Communications library, please implement in the local test environment. |
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.