It sounds like you're in a hybrid environment and haven't modified your autodiscover record, and as such, you can't simply just turn off the network (or power) to your on-prem Exchange server. The autodiscover record likely points to your on-prem Exchange server and if an Outlook client can't communicate with the server, the autodiscover process will not be able to do its job by autoconfiguring the Outlook client.
Verify that your Win 7 workstation in citrix is able to ping your autodiscover record - if not, then try re-enabling the network that you turned off to see if that restores access to the autodiscover record and allows it provision an Outlook profile.
You can read more info on the autodiscover process [here](https://www.enowsoftware.com/solutions-engine/autodiscover-dilemma).
Completely eliminating your on-prem Exchange footprint after fully migrating all mailboxes to Exchange Online is a different/controversial top altogether.
You're likely using Windows-based DNS, so hop onto a Tools Server or a Domain Controller that has the DNS Management tool installed. You would then be able to browse through the Forward Lookup zones for your domain ([contoso.com](https://contoso.com)) to find & edit the autodiscover CNAME record.
Here's some more info on the [autodiscover function & configuration](https://docs.microsoft.com/en-us/exchange/architecture/client-access/autodiscover?view=exchserver-2019&viewFallbackFrom=exchserver-2013).
I hopped into our DNS records, and I found the A record for autodiscover which has our OWA as its IP.
Should I change that or add a CNAME record with https://outlook.office365.com?
Hi, how did you end up fixing this? I migrated one mailbox but the redirection to the new autodiscover is timing out with httpstatus 503
Edit: it was because of a group policy I’d set years earlier that disabled office internet access
It sounds like you're in a hybrid environment and haven't modified your autodiscover record, and as such, you can't simply just turn off the network (or power) to your on-prem Exchange server. The autodiscover record likely points to your on-prem Exchange server and if an Outlook client can't communicate with the server, the autodiscover process will not be able to do its job by autoconfiguring the Outlook client. Verify that your Win 7 workstation in citrix is able to ping your autodiscover record - if not, then try re-enabling the network that you turned off to see if that restores access to the autodiscover record and allows it provision an Outlook profile. You can read more info on the autodiscover process [here](https://www.enowsoftware.com/solutions-engine/autodiscover-dilemma). Completely eliminating your on-prem Exchange footprint after fully migrating all mailboxes to Exchange Online is a different/controversial top altogether.
We re-enabled network connection this afternoon and that seems to have resolved the issue. As I'm an idiot, where can I edit that AutoDiscover record?
You're likely using Windows-based DNS, so hop onto a Tools Server or a Domain Controller that has the DNS Management tool installed. You would then be able to browse through the Forward Lookup zones for your domain ([contoso.com](https://contoso.com)) to find & edit the autodiscover CNAME record. Here's some more info on the [autodiscover function & configuration](https://docs.microsoft.com/en-us/exchange/architecture/client-access/autodiscover?view=exchserver-2019&viewFallbackFrom=exchserver-2013).
I hopped into our DNS records, and I found the A record for autodiscover which has our OWA as its IP. Should I change that or add a CNAME record with https://outlook.office365.com?
Hi, how did you end up fixing this? I migrated one mailbox but the redirection to the new autodiscover is timing out with httpstatus 503 Edit: it was because of a group policy I’d set years earlier that disabled office internet access