![]() Tip: If you cannot connect network and get certain proxy error, you might be interested in this post – Fix: “Windows Could Not Automatically Detect This Network’s Proxy Settings” If Outlook keeps asking for password still, then you can try the following methods provided for you. Therefore, if you encountered this problem, please switch to a more stable network environment at first. It will prompt for password while trying to reconnect. If your network is slow or unstable, Outlook may lose connection to the mail server. ![]() Windows update or upgrade might reset your custom settings for certain apps which can cause this problem. The mentioned problem might appear if there is any problem with your Outlook app settings. Generally speaking, this problem might be caused by several factors listed below. However, while using Outlook, some issues could come forth and one of the common issues is that Outlook keeps asking for password. Outlook, developed by Microsoft, is one of the most widely used online email client platforms. Fix 6: Update Outlook to The Latest Version.Fix 4: Start Outlook in Safe Mode and Disable Add-Ins.Fix 2: Enable “Remember Password” Option.By the way, you can try MiniTool Partition Wizard to better manage hard drive on your Windows 10 PC. If you are troubled by the same problem, just read this article to get 6 effective methods to isolate the issue on Windows 10. If the answer did not help, please add more context/follow-up question for it, and we will help you out.Some Outlook users report that Outlook keeps asking for password even though it is correct. This should also help you get additional information about the credential change, if initiated. I tested it in my automation instance and don't see the behavior where the cred are getting updated/overridden.Īdditionally, any update operation with Automation Account's shared resource (including credential) generates logs, which are available under Activity log of Automation Account. Write-output "smtp_cred - User: $($smtp_cred.UserName) | Password: $($smtp_cred.GetNetworkCredential().Password)" ![]() Write-output "sql_cred - User: $($sql_cred.UserName) | Password: $($sql_cred.GetNetworkCredential().Password)" #Display username and plain text password for both $smtp_cred = Get-AutomationPSCredential -name 'smtp' $sql_cred = Get-AutomationPSCredential -name 'sql' Therefore, you should update the password, if testing on a production instance after performing the test). ( note, this is only recommended for tests as it will display the password in plain text, which will also be later available as job output of the runbook. It might be possible that such cmdlets are altering the content credential from runbook.Īs a test, you can create another runbook, and run the code below to observe the content of the credential ![]() If you notice this specifically happening after the runbook execution, check if the runbook has any update credential operation, for example, presence of cmdlets like Remove-AzAutomationCredential or Set-AzAutomationCredential This could have been through the runbook execution itself or through other means (code run on your machine, manual update etc.). The credentials should not get updated/overridden on its own, unless there has been an update operation. I assume that you are storing the credential in "Credentials" as available in Automation Account's resource menu, as shown below: If I understand the question correctly, the credential stored for Outlook SMTP in Azure Automation is getting overridden. Ha, Thank you for posting the question on Microsoft Q&A.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |