Azure-docs: "Faiure occured in Azure AD application....Try again!!"

[Toouny]

I'm getting the above error in the title when I tried to execute the automated script as I wanted to connect Service Manager, any help please ? :(

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 82e5fdf6-4687-0a17-9a80-07703684b78f
• Version Independent ID: 42ed8d94-6250-54ba-5e8b-de62c0181e82
• Content: Supported connections with IT Service Management Connector in Azure Log Analytics
• Content Source: articles/log-analytics/log-analytics-itsmc-connections.md
• Service: log-analytics
• GitHub Login: @JYOTHIRMAISURI
• Microsoft Alias: v-jysur

[vasivara-MSFT]

@Toouny Thanks for the feedback. We are actively investigating and will get back to you soon.

[vasivara-MSFT]

@Toouny it fails at this part of the code

$adApp = New-AzureRmADApplication -DisplayName $siteName -HomePage $azureSite -IdentifierUris $azureSite -Password $clientSecret

Please double check your variables at the top of the automated script($azureSubscriptionName, $resourceGroupName, $location, $serverName, $domain, $username, $password)

If those are fine, it should be working fine.

[Toouny]

@vasivara-MSFT Thanks Vasivara for you reply, since this is a lab environment, I would like to share the parameters I entered: -

$azureSubscriptionName: I entered the name of my Azure subscription (please mention if any prerequisites are required regarding the Azure Subscription)

$resourceGroupName: I entered the name of the resource group (please mention if any prerequisites are required regarding the resource group)

$location: westeurope

$serverName: scsm1.contoso.com

$domain: contoso

$username: Administrator

$password: Passw0rd!

I ran the script on my SCSM server with the above parameters but still it gives the same error, please mention any prerequisites which should be met.

Can you please provide manual steps to create the Service Manager web App. as an alternative way?

Thanks.

[vasivara-MSFT]

@Toouny If you are using an existing resource group name, Is the location of resourceGroup and $location same?

[Toouny]

Yes :)

[Toouny]

I'm currently checking if my lab environment has an issue and will report back

[Toouny]

Please support if I missed anything

[vasivara-MSFT]

@Toouny I will try to investigate more on monday and I will update you

[Toouny]

Hi Visivara, I figure it out, it is in line 146
I replaced $clientSecret = [System.Web.Security.Membership]::GeneratePassword(30,2).ToString()
with this line $clientSecret = ConvertTo-SecureString "P@ssW0rD!" -AsPlainText -Force

This made the script to continue successfully but it didn't show the $cliensecret at the end it showed it like this Client Secret: System.Security.SecureString

Anyway, I used the value P@ssW0rdD! and it works

[vasivara-MSFT]

@Toouny Thanks for pointing out the issue. I have assigned the issue to the content author to evaluate and update as appropriate.

[Toouny]

Great!

[Toouny]

Please also correct the misspell in the script from Faiure to Failure :)

[vasivara-MSFT]

@Toouny Thank you for your feedback. I have already fixed it when you created this issue. If you take a look at the script right now, you should find it fixed.

[JYOTHIRMAISURI]

@vasivara-MSFT

Hi, discussed with SME (Snehithm), and added the required line in the script, The update is live now. Please see https://github.com/MicrosoftDocs/azure-docs/issues/6515#issuecomment-385450825 for related details. Thanks.

[vasivara-MSFT]

@Toouny We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.