Archiv der Kategorie: Office 365

Connecting to Office 365/Exchange

…..a script with a set of functions to allow me connect to each individual Office 365 service or Exchange Online: Connect-AzureActiveDirectory: Connects to Azure Active Directory Connect-AzureRMS: Connects to Azure Rights Management Connect-ExchangeOnline: Connects to Exchange Online Connect-SkypeOnline: Connects to Skype for Business Online Connect-EOP: Connects to Exchange Online Protection Connect-ComplianceCenter: Connects to Compliance Center Connect-SharePointOnline: Connects to SharePoint Online Connect-MSTeams: Connects to Microsoft Teams Get-Office365Credentials: Gets Office 365 credentials Connect-ExchangeOnPremises: Connects to Exchange On-Premises Get-OnPremisesCredentials: Gets On-Premises credentials Get-ExchangeOnPremisesFQDN: Gets FQDN for Exchange On-Premises Get-Office365Tenant: Gets Office 365 tenant name (SharePoint) Set-Office365Environment: Configures Uri’s and region to use…..

Quelle: Connecting to Office 365/Exchange | EighTwOne (821)

Mailflow issue from Exchange On-Prem to Office 365 – Lalit Bisht Blogs

You are on Exchange Hybrid environment and sending emails to Office 365 via specific SendConnector which has TlsCertificateName attribute configured and EOP is doing certificate validation for Inbound SMTP connections.

You might see any of the following errors in the queue/Protocol Logs.
–> 454 4.7.5 The certificate specified in TlsCertificateName of the SendConnector could not be found.
–> TLS negotiation failed with error NoCredentials.
–> „421 4.4.1 Connection timed out.“ Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts

It may be because of the following issues:
–> You changed the third party SMTP certificate but didn’t update the TlsCertificateName attribute on the send connector.
–> Third party certificate is not assigned to the SMTP services.
–> Status of that third party certificate shows „INVALID“ or „RevocationCheckFailure“.

Please perform the following to resolve the issue.
–> Update the TLSCertificateName attribute on the Office 365 SendConnector.

$cert = Get-ExchangeCertificate -Thumbprint
$TLSCert = (‘<I>’+$cert.issuer+'<S>’+$cert.subject)
Set-SendConnector -Identity -TLSCertificateName $TLSCert
–>Make sure required certificate is assigned to the SMTP service and certificate Status shows VALID.

Quelle: Mailflow issue from Exchange On-Prem to Office 365 – Lalit Bisht Blogs

ADFS 2012 R2 now supports Password Change (not reset) across all devices – samueld

Enabling Change Password in ADFS

By default, this functionality is disabled in ADFS. Change password looks just like another endpoint in ADFS and all you need to do is enable the endpoint. You can use the MMC snapin to enable this.

You can also do this via PSH using the Set-AdfsEndpoint cmdlet.

Once enabled, users can always access the change password page via It would look like this

Quelle: ADFS 2012 R2 now supports Password Change (not reset) across all devices – samueld

Use shared mailbox mobile and other clients

Eine „shared mailbox“ aus Exchange 20XX bzw. Office365 kann nicht einfach auf mobilen Geräten (und anderen, die keinen eigenen Outlook Client installiert haben) genutzt werden. Dazu gibt es aber Lösungen

  1. IMAP-Konfig:
    PW: MyPassword
  2. Konto aktivieren
    Im Active Directory das Konto der „Shared Mailbox“ aktivieren und ein Kennwort festlegen. Dann kann das Postfach wie jedes andere am Client hinzugefügt werden.

Office 365 – Can’t sign in – Error 80041317 | Jack Stromberg

After a long conversation with Microsoft, the end result was somehow federation between Microsoft and our ADFS servers was severed. Here is how we fixed it.

Remote desktop to your ADFS server (not the proxy)

Open the Windows Azure Active Directory Module for Windows PowerShell as an administrator If you are old to ADFS, this was formerly called Microsoft Online Services Module

Execute the following command: Connect-MsolService Type in your Office 365 admin credentials. I highly recommend you use a cloud based user called in the case you cannot federate.

Execute the following command: Update-MsolFederatedDomain Type in the domain name you federate to office 365 ( Successfully updated ‘’ domain. message when done.

Execute the following command: convert-msoldomaintostandard -domainname -passwordfile pass.txt -skipuserconversion $true This command will break federation (essentially turn it off) to Office 365. This will not lose your mailboxes, settings, etc.

Execute the following command: Convert-MsolDomainToFederated This command will re-establish federation to Office 365

Execute the following command: Update-MsolFederatedDomain This command will update URLs or certificate information within AD FS and Office 365. Note: If you have multiple domain names being federated, please use the following command: Update-MSOLFederatedDomain -DomainName -supportmultipledomain

Next, I restarted my proxy server, reran the ADFS wizard to ensure the proxy could communicate to the primary ADFS server, and waited a minute or so.

At this point, authentication began to work properly again.

Quelle: Office 365 – Can’t sign in – Error 80041317 | Jack Stromberg

Must know Office 365 PowerShell commands – TechSultan

Many enterprise migrated to cloud services, especially for email management. Office 365 is one of them, maybe most popular Exchange online solution. If you migrated to Office 365, there is a little adminitrative panel which offer you minimal possibility.

Real administrative tasks are on PowerShell side, it’s hard to find commands and how to operate them, so here a list of must know Office 365 PowerShell commands :

via Must know Office 365 PowerShell commands – TechSultan.