Category: Office365

Yammer and Office 365 groups


“Regarding Azure, it has nothing to do with users or products; you buy upfront a ‘monetary commitment’ and you pick and choose platform(s)/storage/MS apps from the MS cloud environment, so you should see Azure as a ‘Cloud services’ sort of instance which you pay as per you use.

In order to achieve this, we need an Azure Subscription assigned to an O365 account  as it is described here:

Pricing list described here:

Example of services:

Key vault

Azure functions

Storage account with queue


Manage monetary commitments: 


Presentations and how-tos:!Am0e5elsDFPqh-0aW7dYRKY-InN5yg

Change the tenant of a subscription:

Azure and resources access:

There are four main options on how you can configure SSO:


Monitoring SPO (and Onedrive!) performance and slowness:

  • The F12 tool bar network monitor or using third-party tool like fiddler or equivalent

  • SharePoint Online response header metrics (SPRequestDuration and X-SharePointHealthScore)

     SharePoint response header information

  1. Ensure that you have the F12 tools installed. For more information on downloading and installing these tools, see What’s new in F12 tools.

  2. In the F12 tools, on the Network tab, press the green play button to load a page.

  3. Click one of the .aspx files returned by the tool and then click DETAILS.Shows details of the response header
  4. Click Response headers.

    Diagram showing the URL of the response header

Azure AD B2B resources

  • The partner uses their own identities and credentials; Azure AD is not required.
  • You don’t need to manage external accounts or passwords.
  • You don’t need to sync accounts or manage account lifecycles.

Managing externals:

SharePoint Online Azure AD B2B – Custom email invites for users using PowerShell

Powershell to invite B2B users:

External sharing:

with SPO:

with OneDrive:

with MS Teams:

Sharing and collaboration:

B2B Collaboration in Hybrid Identity Scenario

B2B Collaboration in Hybrid Identity Scenario – Part II

Introduction to device management in Azure Active Directory:

As a rule of a thumb, you should use:

  • Azure AD registered devices:
    • For personal devices
    • To manually register devices with Azure AD
  • Azure AD joined devices:
    • For devices that are owned by your organization
    • For devices that are not joined to an on-premises AD
    • To manually register devices with Azure AD
    • To change the local state of a device
  • Hybrid Azure AD joined devices for devices that are joined to an on-premises AD
    • For devices that are owned by your organization
    • For devices that are joined to an on-premises AD
    • To automatically register devices with Azure AD
    • To change the local state of a device

How to Setup:


Azure AD registered devices:


Hybrid Azure AD joined devices:


To configure Hybrid Azure AD joined devices, kindly visit the link:


Azure AD joined devices:


Azure AD Join vs Azure AD Device Registration:


Manage devices:


Device management tasks:


Configure On-Premises Conditional Access using registered devices:



ProxyAddress attribute is used by different applications and it can store different type of user addresses (sip, smtp, x500).

If you sync accounts with non-verified domain to O365, those addresses can be replaced with the default domain.

Some interesting reading regarding this topic:

ADConnect not Syncing ProxyAccount for email Alias from on Premise AD to Azure AD

List of attributes that are synced by the Azure Active Directory Sync Tool

A mail user who has proxy addresses that use non-verified domains isn’t synced in an Exchange hybrid deployment

Wrong domain address when synchronizing from on premise AD

Azure AD Connect sync: Attributes synchronized to Azure Active Directory

Disabling SSL/TLS Protocols and Cipher Suites for ADFS:

Note: dont forget to reboot the WAP and ADFS servers to take effect

To test SSL/TLS and much more you can use the free online tool from Qualys: