Azure Insights: Uninstalling AD Connect; Rate limiting with Istio; Marketplace lead integration

May 1 2021

Azure pros share tips on uninstalling Azure AD Connect, rate limiting with Istio, and using Functions to shift leads from Azure Marketplace to HubSpot.

Is it possible to uninstall Azure AD Connect from Programs and Features?

Microsoft MVP Sander Berkouwer, writing on The Things That Are Better Left Unspoken, looked at a challenge some users face: uninstalling Azure AD Connect after a configuration goes wrong. AD Connect is installed on Windows Server instances but can run into an issue where it won't reconfigure. At this point, admins typically navigating to the Start Menu and the Apps and features option, clicking on the Uninstall button. But then an error message pops up warning of insufficient permissions.

He showed a command line input that resolves the problem. Users will have to run through the uninstall process again.

After Azure AD Connect is correctly removed from the Windows Server, you can start installation and configuration of Azure AD Connect from scratch, or decide to install Azure AD Connect on another Windows Server installation. If your goal is to get rid of Azure AD Connect, then you’ve completed your goal.

Rate limiting with Istio on AKS

Daniel Neumann, writing on Daniel's Tech Blog, revisited a recent walkthrough of the setup for rate limiting reference implementations. Users can also connect the Istio ingress gateway to the ratelimit service, starting off by looking at Istio documentation. Initially, the rate limiting configuration for Istio is connected to the EnvoyFilter object, and implementation is hard. After discussing the failure_mode_deny and cluster_name values, he wrote:

The timeout value defines the time the ratelimit service needs to return a response on a request. It should not be set to high as otherwise your users will experience increased latency on their requests. Especially, when the ratelimit service is temporary unavailable. For Istio and the ratelimit service running on AKS and having the backing Azure Cache for Redis in the same Azure region as AKS I experienced that 25ms for the timeout is a reasonable value.

Neumann recommends other users rely on the Envoy documentation and setup the Envoy filter YAML template to a GitHub repo.

Using Azure Functions to send leads from Azure Marketplace to Hubspot

Wesley Haakman shared a tip on passing leads from Azure Marketplace to Hubspot with Azure Functions. By default, users are unable to send leads directly from Marketplace to Hubspot, but can work around this limitation with Functions, Power Apps or Logic Apps.

To get started, users need the Function App, Hubspot API key and code on their local machine (examples for Visual Studio Code are available in Microsoft documentation). When an outside visitor uses a Marketplace item, a leads get generated which is processed according to configuration as CRM, table storage, or an HTTPS endpoint. Users will often need to create customization around the properties that will end up in Hubspot. After demoing the JSON for the process and how to bring an action, Haakman wrote:

This function still has a lot of stuff that can be added. Think of OAuth (which HubSpot supports), you might not always want to use the APIKey. If you are going to use different endpoints on, you might even need OAuth as not everything is supporting just the APIKey. Also, if you're getting a lot of hits on your marketplace item, some error handling or additional storage (table storage perhaps) would come in handy.

FREE Membership Required to View Full Content:

Become a MemberLogin
Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also have the option to receive periodic email newsletters with the latest relevant articles and content updates. Learn more about us here
About MSCN Reporter

More about MSCN Reporter