Open dabenhamMic opened 2 years ago
ARM related issues @zhoxing-ms
@dabenhamMic We need to confirm whether the REST service returned data to client side. Could you send me the debug log by email? My email address is Zhou.Xing@microsoft.com
disableLocalAuth
hi @zhoxing-ms , here is a link to the api documentation: https://docs.microsoft.com/en-us/rest/api/loganalytics/workspaces/update?tabs=HTTP#workspace
as you see when updating a workspace the response contains Workspace.properties.features which should include disableLocalAuth property.
@dabenhamMic OK, could you send the debug log and output results of CLI to me by email? My email address is Zhou.Xing@microsoft.com
@dabenhamMic OK, could you send the debug log and output results of CLI to me by email? My email address is Zhou.Xing@microsoft.com
I will ask Eduardo Rosa from the Icm to send it to you
@dabenhamMic do you have any update from Eduardo Rosa?
@dabenhamMic do you have any update from Eduardo Rosa?
no update yet
Thank you for your feedback. This has been routed to the support team for assistance.
As I mentioned in ICM, we found that the customer pressed the Ctrl + C
to exit the command execution without waiting for the CLI command to finish from the debug log.
If the CLI command is completed, cli.knack.cli: Event: Cli.SuccessfulExecute []
should be printed in the debug log, but the debug log provided by the customer does not have this log.
I think what the customer may needs to do at present is to wait for the CLI command to finish executing, especially to confirm whether the CLI debug log prints the cli.knack.cli: Event: Cli.SuccessfulExecute []
log
Related command
az resource update
Describe the bug
az resource update --ids \'/subscriptions/fd8f8530-c2c7-413d-84d0-a5ba6f4fd064/resourcegroups/ertv2-prod-ccoe-rg/providers/microsoft.operationalinsights/workspaces/ertv2-prod-ccoe-law\' --set properties.features.disableLocalAuth=true
This gives no output, even though the change seems to occur.
To Reproduce
Expected behavior
Environment summary
Additional context
this is an Icm: https://portal.microsofticm.com/imp/v3/incidents/details/318887747/home