Changing Sales Cycle to long-term customer engagement with Office 365 E Plans

-

Comments

Post a Comment

Popular posts from this blog

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar.
Read more

Wildcard Certificate Support in Skype for Business

-
Coming back to the most common question about certificates in Skype for Business and Lync Server. Can we use Wildcard Certificates in Skype for Business or Lync Server? Simple answer is: YESNO First lets have a look into a certificate: A Certificate has a Common Name (CN) and Subject Alternative Names (SAN) A classic wildcard certificate is a certificate where the CN look like: CN=*.domain.com In Skype for Business the main reason for certificate use is TLS/MTLS data encryption and the other point it the server authentication/ validation. Skype for Business is using the Common Name CN for authentication/ validation trusts. Only if a server with in the Topology or for Federation purposes presents a valid certificate with its matching Common Name (CN) the entire traffic can be used with TLS/MTLS. Therefor we understand a CN identifier as FQDN of the Server or the Pool is RECOMMENDED! A valid SAN Wildcard certificate could look like this: CN   = POOL01.DOMAIN.COM
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more