Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-07-17 Thread Matthew Loraditch 
Oh god, I never replied to this in April.

I posted here what I did that made things work:
https://community.cisco.com/t5/collaboration-applications/oauth-for-office-365-unity-connection-12-5-su2/m-p/4098350#M43230


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Anthony Holloway 
Sent: Friday, July 17, 2020 12:14 PM
To: Matthew Loraditch 
Cc: Dave Goodwin ; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OAuth for Unity Connection/Office 365

[EXTERNAL]

Looks like CUCM 11.5 SU8 addresses oauth with o365.  Did you see that?

On Wed, Apr 22, 2020 at 3:02 PM Anthony Holloway 
mailto:avholloway%2bcisco-v...@gmail.com>> 
wrote:
Matthew, What did you end up learning on this effort?

On Tue, Feb 4, 2020 at 10:10 AM Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>> 
wrote:
I did see that this morning and it fueled my confusion as it’s not needed (or 
useful) when using oauth and the EWS APIs.

They added OAuth because Microsoft is disabling the basic authentication that 
the Autodiscover and the old method used to use.

Really just hoping to get some insight from someone and hope to hear it’s half 
baked and will be finished later and/or I found an issue and it’ll get fixed. 
Will work with TAC eventually if I don’t get any feedback


Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
[cid:image005.jpg@01D65C3F.CC179180]

From: Dave Goodwin mailto:dave.good...@december.net>>
Sent: Tuesday, February 4, 2020 10:32 AM
To: Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>>
Cc: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] OAuth for Unity Connection/Office 365

[EXTERNAL]

Matthew, yes it is pretty new, and I have no setup with which to experiment or 
test, but have you read this section of the CUC 12.x doc? It seems to indicate 
CUC will still use Auto Discovery and in Step 6 it shows how to enable that in 
O365.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5

On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>> 
wrote:
This just came out yesterday so this is more directed for anyone lurking at 
Cisco, but how is this supposed to work?

Our UM has been disabled for months because of MS security requirements for 
resellers that broke the old way so I quickly installed this in my test lab to 
see if it will fix my issue.

According to all the MS documentation there should be no need to use the old 
Autodiscover, etc that Unity was using. You just connect to the default 
outlook.office365.com<http://outlook.office365.com> EWS url and use your oauth 
info and boom.

However, the fields for the old account are still there and mandatory and all 
the test options are going through and failing Autodiscover…

If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying to use 
Oauth/EWS.

Going down the rabbit hole so everyone else doesn’t have to!












Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
[cid:image005.jpg@01D65C3F.CC179180]
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-07-17 Thread Dave Goodwin 
FYI, I recently tried my first O365 Single Inbox integration. I did it
using OAuth2 (my CUC version was 12.5 SU2) and it worked well after I
figured out how to properly use PowerShell to remotely manage Exchange
Online to perform the required steps in the doc. I assume it would work
equally well with 11.5 SU8 if it supports OAuth2.

On Fri, Jul 17, 2020 at 12:14 PM Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Looks like CUCM 11.5 SU8 addresses oauth with o365.  Did you see that?
>
> On Wed, Apr 22, 2020 at 3:02 PM Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
>> Matthew, What did you end up learning on this effort?
>>
>> On Tue, Feb 4, 2020 at 10:10 AM Matthew Loraditch <
>> mloradi...@heliontechnologies.com> wrote:
>>
>>> I did see that this morning and it fueled my confusion as it’s not
>>> needed (or useful) when using oauth and the EWS APIs.
>>>
>>>
>>>
>>> They added OAuth because Microsoft is disabling the basic authentication
>>> that the Autodiscover and the old method used to use.
>>>
>>>
>>>
>>> Really just hoping to get some insight from someone and hope to hear
>>> it’s half baked and will be finished later and/or I found an issue and
>>> it’ll get fixed. Will work with TAC eventually if I don’t get any feedback
>>>
>>>
>>>
>>> Matthew Loraditch​
>>> Sr. Network Engineer
>>> p: *443.541.1518* <443.541.1518>
>>> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
>>> e: *mloradi...@heliontechnologies.com*
>>> 
>>> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>>> [image: Facebook] <https://facebook.com/heliontech>
>>> [image: Twitter] <https://twitter.com/heliontech>
>>> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>>>
>>>
>>>
>>> *From:* Dave Goodwin 
>>> *Sent:* Tuesday, February 4, 2020 10:32 AM
>>> *To:* Matthew Loraditch 
>>> *Cc:* cisco-voip@puck.nether.net
>>> *Subject:* Re: [cisco-voip] OAuth for Unity Connection/Office 365
>>>
>>>
>>>
>>> [EXTERNAL]
>>>
>>>
>>>
>>> Matthew, yes it is pretty new, and I have no setup with which to
>>> experiment or test, but have you read this section of the CUC 12.x doc? It
>>> seems to indicate CUC will still use Auto Discovery and in Step 6 it shows
>>> how to enable that in O365.
>>>
>>>
>>> https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5
>>>
>>>
>>>
>>> On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch <
>>> mloradi...@heliontechnologies.com> wrote:
>>>
>>> This just came out yesterday so this is more directed for anyone lurking
>>> at Cisco, but how is this supposed to work?
>>>
>>>
>>>
>>> Our UM has been disabled for months because of MS security requirements
>>> for resellers that broke the old way so I quickly installed this in my test
>>> lab to see if it will fix my issue.
>>>
>>>
>>>
>>> According to all the MS documentation there should be no need to use the
>>> old Autodiscover, etc that Unity was using. You just connect to the default
>>> outlook.office365.com EWS url and use your oauth info and boom.
>>>
>>>
>>>
>>> However, the fields for the old account are still there and mandatory
>>> and all the test options are going through and failing Autodiscover…
>>>
>>>
>>>
>>> If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying
>>> to use Oauth/EWS.
>>>
>>>
>>>
>>> Going down the rabbit hole so everyone else doesn’t have to!
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Matthew Loraditch**​*
>>>
>>> *Sr. Network Engineer*
>>>
>>> p: *443.541.1518* <443.541.1518>
>>>
>>> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>>>
>>>  |
>>>
>>> e: *mloradi...@heliontechnologies.com*
>>> 
>>>
>>> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>>>
>>> [image: Facebook] <https://facebook.com/heliontech>
>>>
>>> [image: Twitter] <https://twitter.com/heliontech>
>>>
>>> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>>>
>>> ___
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>> ___
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-07-17 Thread Anthony Holloway 
Looks like CUCM 11.5 SU8 addresses oauth with o365.  Did you see that?

On Wed, Apr 22, 2020 at 3:02 PM Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Matthew, What did you end up learning on this effort?
>
> On Tue, Feb 4, 2020 at 10:10 AM Matthew Loraditch <
> mloradi...@heliontechnologies.com> wrote:
>
>> I did see that this morning and it fueled my confusion as it’s not needed
>> (or useful) when using oauth and the EWS APIs.
>>
>>
>>
>> They added OAuth because Microsoft is disabling the basic authentication
>> that the Autodiscover and the old method used to use.
>>
>>
>>
>> Really just hoping to get some insight from someone and hope to hear it’s
>> half baked and will be finished later and/or I found an issue and it’ll get
>> fixed. Will work with TAC eventually if I don’t get any feedback
>>
>>
>>
>> Matthew Loraditch​
>> Sr. Network Engineer
>> p: *443.541.1518* <443.541.1518>
>> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
>> e: *mloradi...@heliontechnologies.com*
>> 
>> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>> [image: Facebook] <https://facebook.com/heliontech>
>> [image: Twitter] <https://twitter.com/heliontech>
>> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>>
>>
>>
>> *From:* Dave Goodwin 
>> *Sent:* Tuesday, February 4, 2020 10:32 AM
>> *To:* Matthew Loraditch 
>> *Cc:* cisco-voip@puck.nether.net
>> *Subject:* Re: [cisco-voip] OAuth for Unity Connection/Office 365
>>
>>
>>
>> [EXTERNAL]
>>
>>
>>
>> Matthew, yes it is pretty new, and I have no setup with which to
>> experiment or test, but have you read this section of the CUC 12.x doc? It
>> seems to indicate CUC will still use Auto Discovery and in Step 6 it shows
>> how to enable that in O365.
>>
>>
>> https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5
>>
>>
>>
>> On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch <
>> mloradi...@heliontechnologies.com> wrote:
>>
>> This just came out yesterday so this is more directed for anyone lurking
>> at Cisco, but how is this supposed to work?
>>
>>
>>
>> Our UM has been disabled for months because of MS security requirements
>> for resellers that broke the old way so I quickly installed this in my test
>> lab to see if it will fix my issue.
>>
>>
>>
>> According to all the MS documentation there should be no need to use the
>> old Autodiscover, etc that Unity was using. You just connect to the default
>> outlook.office365.com EWS url and use your oauth info and boom.
>>
>>
>>
>> However, the fields for the old account are still there and mandatory and
>> all the test options are going through and failing Autodiscover…
>>
>>
>>
>> If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying
>> to use Oauth/EWS.
>>
>>
>>
>> Going down the rabbit hole so everyone else doesn’t have to!
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Matthew Loraditch**​*
>>
>> *Sr. Network Engineer*
>>
>> p: *443.541.1518* <443.541.1518>
>>
>> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>>
>>  |
>>
>> e: *mloradi...@heliontechnologies.com*
>> 
>>
>> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>>
>> [image: Facebook] <https://facebook.com/heliontech>
>>
>> [image: Twitter] <https://twitter.com/heliontech>
>>
>> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-04-22 Thread Anthony Holloway 
Matthew, What did you end up learning on this effort?

On Tue, Feb 4, 2020 at 10:10 AM Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:

> I did see that this morning and it fueled my confusion as it’s not needed
> (or useful) when using oauth and the EWS APIs.
>
>
>
> They added OAuth because Microsoft is disabling the basic authentication
> that the Autodiscover and the old method used to use.
>
>
>
> Really just hoping to get some insight from someone and hope to hear it’s
> half baked and will be finished later and/or I found an issue and it’ll get
> fixed. Will work with TAC eventually if I don’t get any feedback
>
>
>
> Matthew Loraditch​
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
> e: *mloradi...@heliontechnologies.com* 
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
> [image: Facebook] <https://facebook.com/heliontech>
> [image: Twitter] <https://twitter.com/heliontech>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
>
> *From:* Dave Goodwin 
> *Sent:* Tuesday, February 4, 2020 10:32 AM
> *To:* Matthew Loraditch 
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] OAuth for Unity Connection/Office 365
>
>
>
> [EXTERNAL]
>
>
>
> Matthew, yes it is pretty new, and I have no setup with which to
> experiment or test, but have you read this section of the CUC 12.x doc? It
> seems to indicate CUC will still use Auto Discovery and in Step 6 it shows
> how to enable that in O365.
>
>
> https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5
>
>
>
> On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch <
> mloradi...@heliontechnologies.com> wrote:
>
> This just came out yesterday so this is more directed for anyone lurking
> at Cisco, but how is this supposed to work?
>
>
>
> Our UM has been disabled for months because of MS security requirements
> for resellers that broke the old way so I quickly installed this in my test
> lab to see if it will fix my issue.
>
>
>
> According to all the MS documentation there should be no need to use the
> old Autodiscover, etc that Unity was using. You just connect to the default
> outlook.office365.com EWS url and use your oauth info and boom.
>
>
>
> However, the fields for the old account are still there and mandatory and
> all the test options are going through and failing Autodiscover…
>
>
>
> If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying to
> use Oauth/EWS.
>
>
>
> Going down the rabbit hole so everyone else doesn’t have to!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Matthew Loraditch**​*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *mloradi...@heliontechnologies.com* 
>
> [image: Helion Technologies] <http://www.heliontechnologies.com/>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-02-04 Thread Matthew Loraditch 
I did see that this morning and it fueled my confusion as it’s not needed (or 
useful) when using oauth and the EWS APIs.

They added OAuth because Microsoft is disabling the basic authentication that 
the Autodiscover and the old method used to use.

Really just hoping to get some insight from someone and hope to hear it’s half 
baked and will be finished later and/or I found an issue and it’ll get fixed. 
Will work with TAC eventually if I don’t get any feedback



Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Dave Goodwin 
Sent: Tuesday, February 4, 2020 10:32 AM
To: Matthew Loraditch 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] OAuth for Unity Connection/Office 365

[EXTERNAL]

Matthew, yes it is pretty new, and I have no setup with which to experiment or 
test, but have you read this section of the CUC 12.x doc? It seems to indicate 
CUC will still use Auto Discovery and in Step 6 it shows how to enable that in 
O365.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5

On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>> 
wrote:
This just came out yesterday so this is more directed for anyone lurking at 
Cisco, but how is this supposed to work?

Our UM has been disabled for months because of MS security requirements for 
resellers that broke the old way so I quickly installed this in my test lab to 
see if it will fix my issue.

According to all the MS documentation there should be no need to use the old 
Autodiscover, etc that Unity was using. You just connect to the default 
outlook.office365.com<http://outlook.office365.com> EWS url and use your oauth 
info and boom.

However, the fields for the old account are still there and mandatory and all 
the test options are going through and failing Autodiscover…

If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying to use 
Oauth/EWS.

Going down the rabbit hole so everyone else doesn’t have to!












Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
[cid:image006.jpg@01D5DB46.F99D31C0]
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] OAuth for Unity Connection/Office 365

2020-02-04 Thread Dave Goodwin 
Matthew, yes it is pretty new, and I have no setup with which to experiment
or test, but have you read this section of the CUC 12.x doc? It seems to
indicate CUC will still use Auto Discovery and in Step 6 it shows how to
enable that in O365.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-05f5

On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:

> This just came out yesterday so this is more directed for anyone lurking
> at Cisco, but how is this supposed to work?
>
>
>
> Our UM has been disabled for months because of MS security requirements
> for resellers that broke the old way so I quickly installed this in my test
> lab to see if it will fix my issue.
>
>
>
> According to all the MS documentation there should be no need to use the
> old Autodiscover, etc that Unity was using. You just connect to the default
> outlook.office365.com EWS url and use your oauth info and boom.
>
>
>
> However, the fields for the old account are still there and mandatory and
> all the test options are going through and failing Autodiscover…
>
>
>
> If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying to
> use Oauth/EWS.
>
>
>
> Going down the rabbit hole so everyone else doesn’t have to!
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Matthew Loraditch​
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com*   |
> e: *mloradi...@heliontechnologies.com* 
> [image: Helion Technologies] 
> [image: Facebook] 
> [image: Twitter] 
> [image: LinkedIn] 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] OAuth for Unity Connection/Office 365

2020-02-04 Thread Matthew Loraditch 
This just came out yesterday so this is more directed for anyone lurking at 
Cisco, but how is this supposed to work?

Our UM has been disabled for months because of MS security requirements for 
resellers that broke the old way so I quickly installed this in my test lab to 
see if it will fix my issue.

According to all the MS documentation there should be no need to use the old 
Autodiscover, etc that Unity was using. You just connect to the default 
outlook.office365.com EWS url and use your oauth info and boom.

However, the fields for the old account are still there and mandatory and all 
the test options are going through and failing Autodiscover...

If I look at the Mailbox Sync Logs I don't see any evidence it's trying to use 
Oauth/EWS.

Going down the rabbit hole so everyone else doesn't have to!












Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip