Forum Widgets
Latest Discussions
Want to check email already exists or not before verifying email in signup of Azure AD B2C flow.
I'm working on a custom sign-up flow in Azure AD B2C, and I want to include a step to check whether an email address already exists before initiating the email verification process. The goal is to enhance the user experience by avoiding unnecessary verification for existing email addresses. I'm looking for guidance on how to configure a custom user journey that incorporates a technical profile specifically designed to validate the uniqueness of the provided email address. Ideally, I want to collect the user's email, check if it exists, and then proceed with email verification only if the email is new. If anyone has experience implementing such a scenario or can provide insights into the necessary steps and configurations, I would greatly appreciate your assistance. Additionally, any code snippets or examples related to this specific use case would be extremely helpful. Thank you in advance for your support!Logic Apps Data Mapper Integer Formatting Issue
Hello team, I am working on a data map that is giving me a hard time in the logic app. For my transformations, I do json-to-json transformation using the new data mapper. I have managed to handle all fields but for some reason one integer field is giving me a very hard time. <number key="id"> <xsl:value-of select="/*/*[@key='mapparameters']/*[@key='counterpartyType1id']" /> </number> Here, if I pass let's say 12345, I want to see 12345 but the result is 12345.0. This action's output is directly being sent to a HTTP call in the logic app and based on the workflow run logs, everything seems okay. In the logs, the value seen as 12345. However, when we check the backend, this field is 12345.0 in the request body and this causes an error as the application does not accept it. I tried to format the number and convert it in any way but with no luck, the issue is this problem started happening out of the blue someday. Does anyone can guide me a potential resolution? Thanks.
BTDF Extentions for VS 2019 | BizTalk 2020 Deployment Framework | Visual Studio 2019 Extentions
Hi all, if somebody needs a BTDF 2020 Extentions for VS 2019 we are glad to help: https://datapassion.de/index.php/dpnews/btdf-extentions-for-vs-2019-biztalk-deployment-framework-2020-visual-studio-2019-extentions
Issue with Custom Domain on APIM and Cloudflare Proxying
Dear all, Last week, we attempted to configure a custom domain name for our Azure API Management (APIM) instance. We use Cloudflare as our DNS provider. The required CNAME record was created with the proxied attribute enabled. However, when configuring the custom hostname in Azure, we encountered the following error: Invalid parameter: CustomHostnameOwnershipCheckFailed. A CNAME record pointing from apim.ourowndomain.net to apim.azure-api.net was not found. As a workaround, we disabled the proxied attribute in Cloudflare, retried the configuration, and it worked successfully. We then re-enabled the proxied attribute, and the custom domain continued to function correctly. However, yesterday, we discovered that the custom domain was no longer working and returned a "404 Web site not found" error page. After extensive troubleshooting—including disabling the proxied attribute on the CNAME record—we were unable to resolve the issue. To restore functionality, we removed and reconfigured the custom domain by following the same steps: Disable the proxied attribute on the CNAME record. Configure the custom domain in APIM. Re-enable the proxied attribute. This resolved the issue again. We suspect that Azure initially validates the CNAME record during the custom domain configuration process when the proxied attribute is disabled. However, after a few days, Azure appears to revalidate the CNAME record and expects it to resolve to *.azure-api.net. Since Cloudflare returns its own IPs when proxying is enabled, Azure may reject the custom domain configuration, leading to the issue. Can anyone confirm whether our assumption is correct? Additionally, is there a recommended workaround for this issue? We are considering deploying a reverse proxy (Application Gateway) to handle Cloudflare requests and forward them to the APIM instance. Thank you in advance for your help. Best regards,
Azure elastic cloud with private endpoint
Hello, Currently, I'm utilizing Elastic Cloud on Azure and aiming to secure it through Private Link. I've established a private endpoint with a private DNS zone in Azure and incorporated a DNS forwarder. However, when I ping "elastic-name.kb.privatelink.westeurope.azure.elastic-cloud.com," I receive the private IP. Yet, when pinging "elastic-name.kb.westeurope.azure.elastic-cloud.com," I get the public IP, which differs from the typical behavior of Azure resources. I've tested other resources like blobs, files, and app services, and consistently received private IPs for both. Do you have any insights into why Elastic behaves in this manner? Thank you for your assistance in advance.Microsoft Entra SSO integration with FortiGate SSL VPN issue
Scenario: Microsoft Entra SSO integration with FortiGate SSL VPN I am unable to connect via FortiClient vpn version 7.2.x.x. But when i use FortiClient vpn client version 7.0.x.x.x to connect SSL VPN via Azure ID with SAML Authentication. its connect in 2nd attempt or 3rd attempt every time not in first attempt. In first attempt ask 2FA but not connected. when i try again in 2nd or 3rd attempt so without 2FA prompt just directly connected. is it bug or configuration issue on FortiClient firewall side or Azure FortiGate SSL VPN application side?? please suggest
