Microsoft Teams
A Microsoft customizable chat-based workspace.
10,894 questions
these often occurs due to issues with the authentication process or network connectivity.
Error while connecting to MSOLService, Teams and IPPSsession using basic auth
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 14.000000000000002%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAG%3C/text%3E%3C/svg%3E)
Ananda Gedela
1
Reputation point
While connecting to the MSOL service, Teams and IPPSSession using the powershell with Basic Auth(MFA disabled and necessry roles added), facing the below issue
Commands Ran:
$cred = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $username, $(convertto-securestring $password -asplaintext -force)
Connect-IPPSSession -Credential $cred
Connect-MsolService -Credential $cred
"errorMessage":"An error occurred while sending the request.","errorStackTrace":" at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.Identity.Core.Http.HttpManager.<ExecuteAsync>d__9.MoveNext() in D:\\a\\1\\s\\src\\Microsoft.IdentityModel.Clients.ActiveDirectory\\Core\\Http\\HttpManager.cs:line 235\r\n--- End of stack trace from previous location "
Can anybody please help us in resolving this issue
Microsoft Teams
PowerShell
PowerShell
A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
2,922 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
24,332 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 49%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
LiweiTian-MSFT 25,935 Reputation points Microsoft External Staff2023-08-08T09:28:04.9833333+00:00 Hi
Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is not in our support scope. Thanks for your understanding and patience.
Sign in to comment
2 answers
Sort by: Most helpful
-
NAZIFI ADAM 1 Reputation point2023-08-08T06:14:23.27+00:00 -
Ananda Gedela 1 Reputation point
2023-08-08T07:35:00.0666667+00:00 We are actually triggering it from, the azure app service(function app with PowerShell has the environment).
Sign in to comment -
-
Brian Zarb 1,670 Reputation points2023-08-08T06:25:40.9566667+00:00 Instead Install the Azure module (install-module) and use the Connect-AzureAD to connect, here is how i typically do it:
$securepass = ConvertTo-SecureString "Plainpassword" -AsPlainText -Force Connect-AzureAD -Credential (new-object system.management.automation.PScredential("******@email.com",$securepass)) -showbanner:$falseThis has worked several time for me , hopefully it does for you to.
If you find this helpful, consider leaving a thumbs up and mark as your answer.
-
Ananda Gedela 1 Reputation point
2023-08-08T07:36:23.9266667+00:00 tried this but still the same issue
-
Brian Zarb 1,670 Reputation points
2023-08-08T07:38:15.52+00:00 Can you give us some more insight, post the error you are getting
-
Ananda Gedela 1 Reputation point
2023-08-08T08:52:39.42+00:00 yeah, actually we have a azure function app deployed on our tenant, which consists of azure functions with the Powershell has the runtime env.
In this, we are trying to connect to msol service with basic auth using service account creds(MFA disable), after the connection we run some cmdlets and wrap it has a output.
But while connecting to the Msol itself is failing with the above error. Want to know, if any points that needs to be checked against the user, anything needs to be disabled etc.
-
Brian Zarb 1,670 Reputation points
2023-08-08T15:48:18.3333333+00:00 I believe that Microsoft might have deprecated Basic Authentication. Connect-AzureAD uses modern auth while Connect-MSol uses basic auth
- If you're using an application to connect:
- Register your application in the Azure AD portal.
- Grant the necessary permissions for your application.
- Use the application's client ID, secret, and the specific OAuth2 endpoint to obtain an access token. This token can then be used to authenticate your requests.
- Grant the necessary permissions for your application.
- Register your application in the Azure AD portal.
- Service Principals and Managed Identities: If your script or application runs within Azure (e.g., Azure Functions, VMs), consider using Managed Identities. This allows Azure resources to authenticate to services that support Azure AD authentication without needing to store credentials in your code.
- Update Scripts & Applications: If you have legacy scripts or applications relying on Basic Authentication, they will need to be updated to use Modern Authentication methods.
Also, this can be caused by a connection issue, check your proxy settings, or firewall barriers. Ensure there's unhindered access to Microsoft's services.
Last thing is , make sure you're using the latest AzureAD or AzureADPreview modules in your Azure Functions. Outdated or incompatible modules might cause connection issues.
- If you're using an application to connect:
Sign in to comment -