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
For the DontShow parameters like -Proxy or -AppendPipeline, although we are hiding them from the online doc, but when the in-tool help still displays those parameters.
We should consider being more descriptive, add works like "This cmdlet is for internal use only........".
The text was updated successfully, but these errors were encountered:
In the medium to long term, would there be an opportunity to do the internal mock testing using these parameters, then a second export without them, this would eliminate the issue entirely.
In the short term we should definitely tell customers that these parameters are for internal MSFT use only.
For [-Break] [-HttpPipelineAppend] [-HttpPipelinePrepend], which are for internal use, will add descriptions to tell users they are for internal use only.
For [-Proxy] [-ProxyCredential], [-ProxyUseDefaultCredentials], which are used to support cmdlet level proxy. Will add description to recommend users to use system level proxy support. And if usage is low, will considering to deprecate cmdlet level proxy support.
For the DontShow parameters like -Proxy or -AppendPipeline, although we are hiding them from the online doc, but when the in-tool help still displays those parameters.
We should consider being more descriptive, add works like "This cmdlet is for internal use only........".
The text was updated successfully, but these errors were encountered: