I tried removing the route table from the Subnet the App Service was running on, but still encountered the same issue. Was there another change needing to be made, perhaps on the VNET/subnet itself, or the way the company created it internally?
To be honest we went with a totally different approach.
The only solution I was told was not to check these outgoing addresses at the company level, which we obviously didn't do.
The service we called was internal and we implemented event driven architecture to not rely on it and to be more fault tolerant.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I tried removing the route table from the Subnet the App Service was running on, but still encountered the same issue. Was there another change needing to be made, perhaps on the VNET/subnet itself, or the way the company created it internally?
To be honest we went with a totally different approach.
The only solution I was told was not to check these outgoing addresses at the company level, which we obviously didn't do.
The service we called was internal and we implemented event driven architecture to not rely on it and to be more fault tolerant.