-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Script stopped working #22
Comments
Are you sure that the user is excluded? That portion of the script doesn't depend on application impersonation or EWS. I'd suggest you double-check the credentials. You can test by manually running the below code in a PowerShell window. It should return a list of all users.
|
It’s erroring out. Here’s the error message:
[cid:image002.jpg@01D6B38A.225F54A0]
From: Ryan Graham <notifications@github.com>
Sent: Thursday, November 5, 2020 3:38 PM
To: grahamr975/EWS-Office365-Contact-Sync <EWS-Office365-Contact-Sync@noreply.github.com>
Cc: Dino Maglinte <DMaglinte@ChoicesCCS.org>; Author <author@noreply.github.com>
Subject: Re: [grahamr975/EWS-Office365-Contact-Sync] Script stopped working (#22)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Are you sure that the user is excluded? That portion of the script doesn't use application impersonation or EWS. I'd suggest you double-check the credentials. You can test by manually running the below code in a PowerShell window.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $ConnectionUri -Credential Get-Credential -Authentication Basic -AllowRedirection
Import-PSSession $Session -DisableNameChecking -AllowClobber
# Import Global Address List into Powershell from Office 365 Exchange as an array
$ContactList = Get-User -ResultSize unlimited
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#22 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQWKRCW2ANX3CLNOWLCCBH3SOMEIXANCNFSM4TJIDUNA>.
|
@dmaglinte77 I don't see the error message? |
Yep, definitely looks like an authentication issue with the account you're using. Could be one or more of the below issues:
I'd suggest you follow Microsoft's troubleshooting guide here and verify that basic authentication is enabled for the account. |
Good morning! PS>TerminatingError(Connect-EXCExchange): "Exception calling "AutodiscoverUrl" with "2" argument(s): "The Autodiscover service couldn't be located.""
|
Looks like you're using basic EWS authentication (Negotiate Auth), which your environment is probably also blocking. Can you try using the latest version of the script along with the -ModernAuth flag? Make sure to follow the new instructions found in the read me. |
No dice. I re-downloaded your code and ran it again. Made sure -ModernAuth was set, but still getting that same error message. |
@dmaglinte77 The newest version of the script now uses an AzureApp so it completely bypasses MFA-related issues. Please update and follow the guide in the README.md to resolve this issue. |
I'd recommend updating soon. Microsoft will depreciate basic authentication (used by the old script) on October 1st, 2022. Tenets will have the opportunity to manually delay the depreciation until December 31st, 2022 on a per-protocol basis. See below. |
This script stopped working for me at the end of september. MFA has been enabled in our tenant, but the user that I'm using to for the script has been excluded. But no matter what I do I cannot seem to get the script to work. Has anyone else seen this issue?
The text was updated successfully, but these errors were encountered: