Mes: diciembre 2021

Microsoft 365: Public Preview of Multi-tenant Sync support with Azure AD Connect!

Posted by

0

Undoubtedly, the public preview of multi-tenant sync support with Azure AD Connect is one of the biggest news we were waiting for. This new feature will allow the possibility to synchronize the same AD object to multiple Azure ADs through Azure AD Connect. You can find all the details in the following URL:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies

The full details of what’s supported in this scenario are the following:

  • AADConnect can synchronize the same users, groups, and contacts from a single Active Directory to multiple Azure AD tenants. These tenants can be in different Azure environments, such as the Azure China environment or the Azure Government environment, but they could also be in the same Azure environment, such as two tenants that are both in Azure Commercial.

  • The same Source Anchor can be used for a single object in separate tenants (but not for multiple objects in the same tenant)

  • You will need to deploy an AADConnect server for every Azure AD tenant you want to synchronize to – one AADConnect server cannot synchronize to more than one Azure AD tenant.

  • It is supported to have different sync scopes and different sync rules for different tenants.

  • Only one Azure AD tenant sync can be configured to write back to Active Directory for the same object. This includes device and group writeback as well as Hybrid Exchange configurations – these features can only be configured in one tenant. The only exception here is Password Writeback – see below.

  • It is supported to configure Password Hash Sync from Active Directory to multiple Azure AD tenants for the same user object. If Password Hash Sync is enabled for a tenant, then Password Writeback may be enabled as well, and this can be done on multiple tenants: if the password is changed on one tenant, then password writeback will update it in Active Directory, and Password Hash Sync will update the password in the other tenants.

  • It is not supported to use the same custom domain name in more than one Azure AD tenant, with one exception: it is supported to use a custom domain name in the Azure Commercial environment and use that same domain name in the Azure GCCH environment. Note that the custom domain name MUST exist in Commercial before it can be verified in the GCCH environment.

  • It is not supported to configure hybrid experiences such as Seamless SSO and Hybrid Azure AD Join on more than one tenant. Doing so would overwrite the configuration of the other tenant and would make it unusable.

  • You can synchronize device objects to more than one tenant but only one tenant can be configured to trust a device.

  • Each Azure AD Connect instance should be running on a domain-joined machine.

Microsoft 365: Filter Options in the Activity Feed in Microsoft Teams (I)!

Posted by

0

As happens with Private Chats in Microsoft Teams, in the activity feed we also have the possibility to choose and apply different filters available:

image

As you can see, we can choose one of the following filters: Unread, Mentions, Replies, Reactions, Missed call, Voice mail o Apps. For now, it’s only possible to choose one filter what it’s quite limited in mi opinion.

image

Microsoft 365: Opciones de filtro en el Feed de actividad de Microsoft Teams (I)!

Posted by

0

Al igual que sucede con los chats privados de Teams, en el Feed de actividad tenemos la posibilidad no solo de buscar mediante texto libre, sino también de aplicar alguno de los filtros disponibles:

image

Como se puede apreciar, podemos escoger entre los siguientes filtros: Unread, Mentions, Replies, Reactions, Missed call, Voice mail o Apps. Por el momento no es posible aplicar más de un filtro y estamos limitados a seleccionar uno solo.

image

Microsoft 365: Multi-tenant Sync con Azure AD Connect en Public Preview!

Posted by

0

Sin duda, gran noticia el que finalmente podamos tener soporte para sincronizar un mismo DA con diferentes Azure AD gracias al soporte de este escenario en Azure AD Connect. Este escenario está actualmente en Public Preview como podéis ver en la documentación correspondiente:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies

El detalle concreto de que se soporta en este escenario es el siguiente:

  • AADConnect can synchronize the same users, groups, and contacts from a single Active Directory to multiple Azure AD tenants. These tenants can be in different Azure environments, such as the Azure China environment or the Azure Government environment, but they could also be in the same Azure environment, such as two tenants that are both in Azure Commercial.

  • The same Source Anchor can be used for a single object in separate tenants (but not for multiple objects in the same tenant)

  • You will need to deploy an AADConnect server for every Azure AD tenant you want to synchronize to – one AADConnect server cannot synchronize to more than one Azure AD tenant.

  • It is supported to have different sync scopes and different sync rules for different tenants.

  • Only one Azure AD tenant sync can be configured to write back to Active Directory for the same object. This includes device and group writeback as well as Hybrid Exchange configurations – these features can only be configured in one tenant. The only exception here is Password Writeback – see below.

  • It is supported to configure Password Hash Sync from Active Directory to multiple Azure AD tenants for the same user object. If Password Hash Sync is enabled for a tenant, then Password Writeback may be enabled as well, and this can be done on multiple tenants: if the password is changed on one tenant, then password writeback will update it in Active Directory, and Password Hash Sync will update the password in the other tenants.

  • It is not supported to use the same custom domain name in more than one Azure AD tenant, with one exception: it is supported to use a custom domain name in the Azure Commercial environment and use that same domain name in the Azure GCCH environment. Note that the custom domain name MUST exist in Commercial before it can be verified in the GCCH environment.

  • It is not supported to configure hybrid experiences such as Seamless SSO and Hybrid Azure AD Join on more than one tenant. Doing so would overwrite the configuration of the other tenant and would make it unusable.

  • You can synchronize device objects to more than one tenant but only one tenant can be configured to trust a device.

  • Each Azure AD Connect instance should be running on a domain-joined machine.