I am still working on an API Manager DR scenario for a client. After automating the backup and restore process, to make sure that the APIM instances are always in sync, I needed to setup Traffic Manager in priority mode to distribute the calls between the main and secondary instances.
Traffic Manager setup seemed quite straightforward. You just need to create a traffic manager endpoint for each API Manager Instance, using the external endpoint.
Creating that for each endpoint should do the trick… Or so I thought. After that setup was complete, testing the endpoint always returned 503, even though access each individual endpoint was returning the correct result.
Today I’ve received a very special email – the renewal of my MVP Award for the period 2018-2019. Those who had received the award before knows how cherished is the moment that you see the email on your inbox. The best part of the award is the confirmation that what you are doing is been recognized as having an impact on the community – which is the reason why you do the work in the first place. The renewal shows that you didn’t lose steam, but keep going in the right direction. But it wouldn’t be a post about the MVP Award, without recognizing the support network behind me that gives me the chance to do all the community contribution I do. Continue reading “And the Cycle Starts Again”
When it comes to developing Logic Apps, everyone has a preference. Some people like to develop in the portal, while others like to start development directly from Visual Studio. I am in the first group mainly because a lot of my logic apps involves integration with the Dynamics 365 CRM connector, which doesn’t play well with the Logic Apps editor after I apply the required parameterization (which reminds me that I have to blog about that – will write something about it soon). I also like the simplicity of just opening the browser and be able to develop, debug all in one go.