bjblackmore
asked on
Modify Send Connector on Office 365
I need to modify one of the send connector we have setup in our Office 365 implimentation, to require TLS. I have tried using the below powershell commands, but these all error with:
"Set-SendConnector : The operation couldn't be performed because object 'PartnerCo Outbound' couldn't be found on 'DomainController1.ourdoma in.local"
#connect to Exchange Online
$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session –AllowClobber
add-pssnapin Microsoft.Exchange.Managem ent.PowerS hell.E2010
#modify send connector
Set-sendconnector –identity “PartnerCo Outbound” –requiretls $true
#Using Online Domain as a prefix:
Set-sendconnector –identity “CloudDomain\PartnerCo Outbound” –requiretls $true
#Using GUI:
Set-sendconnector –identity 74930198-55f9-4e5b-ba36-7f b3cf473f1e –requiretls $true
How can I connect to Office 365 and modify the send connector?
"Set-SendConnector : The operation couldn't be performed because object 'PartnerCo Outbound' couldn't be found on 'DomainController1.ourdoma
#connect to Exchange Online
$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session –AllowClobber
add-pssnapin Microsoft.Exchange.Managem
#modify send connector
Set-sendconnector –identity “PartnerCo Outbound” –requiretls $true
#Using Online Domain as a prefix:
Set-sendconnector –identity “CloudDomain\PartnerCo Outbound” –requiretls $true
#Using GUI:
Set-sendconnector –identity 74930198-55f9-4e5b-ba36-7f
How can I connect to Office 365 and modify the send connector?
ASKER
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, that seems to have sorted it!
Open in new window
part of your script, using this will send the cmdlets to your on-prem server