Ad connect - what data from Teams will be missing - active-directory

My organisation use Active Directory on-premise (windows server 2012). We also use Office 365 E1.
Logins are different. We add accounts independly.
Now we are however are thinking about using Ad Connect, but we have some concerns.
Will we lose any data on Teams after integration?
Will our users be able to access data previously attached to theirs Azure Active Directory account?
How can we match AAD users with on-premise AD. It uses aliases?

Following MS documents should give a head start for your requirement.
How objects and credentials are synchronized in an Azure Active Directory Domain Services managed domain
Integrate on-premises AD with Azure
Integrate on-premises AD domains with Azure AD
Azure AD Connect: When you have an existing tenant
Microsoft 365 integration with on-premises environments

Related

Can Azure AD MFA work with on-prem Active Directory?

Can Azure AD MFA work with on-prem Active Directory? Our entire infrastructure is Microsoft on-prem solutions (AD, Exchange, SQL, SharePoint, Office, etc). We do have Microsoft 365 Basic which allows us to use the free version of Azure AD. We currently have our AD accounts synchronizing between on-prem and Azure AD. I've got MFA enabled for Azure AD, but it only works when signing into something Azure related. If I sign into an on-prem AD-joined device, it doesn't recognize I have MFA enabled in Azure AD for my user account.
we have two options available.
To trigger Azure MFA on RDP to On-premises VMs or to connect to On-premises VPN etc.The Network Policy Server (NPS) extension for Azure allows customers to safeguard Remote Authentication Dial-In User Service (RADIUS) client authentication using Azure's cloud-based Multi-Factor Authentication (MFA). this enables secure verification for users attempting to sign in to a Remote Desktop Gateway.
check This to Integrate your Remote Desktop Gateway infrastructure using the Network Policy Server (NPS) extension and Azure AD
To protect On-premises web applications, such as OWA, SharePoint etc., they need to federate the web applications to ADFS and configure ADFS to use Azure MFA for 2nd factor of authentication. If your organization is federated with Azure AD, you can use Azure Multi-Factor Authentication to secure AD FS resources, both on-premises and in the cloud. reference

Azure AD integration with Office 365

Hello and thank you for reading.
We have Office 365 users and licenses and have recently moved into Azure. We want to connect these together.
I have created a domain controller but am unsure on how to add our existing domain in.
I have tried Azure AD Connect but it asks for 'AD Domain Services administrator', which we do not have. We have no on-premise AD at all, we want to start fresh in the cloud.
Any info would be greatly appreciated.
Thank you
If you have Office 365 license then you will have Azure Active directory services by default.
If you don't have any on-premises domain then there is no need for Azure AD connect.
Azure AD connect is used to sync the users from on-prem AD to Azure AD.
In order to add and register your existing domain in Azure , please follow this article (domain controller is not needed)

Is it possible to authenticate for access to SSAS (on-premise) using Azure Active Directory credentials

I have an on-premises 2019 (15) instance of SSAS in tabular mode. I also have an Azure Active Directory with multiple users.
When connecting to the SSAS instance through SSMS there are 3 available authentication methods:
Windows.
Active Directory - with password
Active Directory - universal with MFA
I am returned the following message when trying to authenticate with 2 or 3:
Cannot connect to xxxxx\xxxxxx. The integrated security 'ClaimsToken'
is not supported for native connections.
(Microsoft.AnalysisServices.AdomdClient)
How do I make it possible for AAD users to authenticate for access to on-prem use of SSAS?
The modes you are looking at are available for Azure Sql Databases that have been protected with an Azure AD tenant.
On-prem SQL Server and its add-ons do not support authenticating with Azure AD.

Azure Active Directory to new Windows 2019 Server

we have been using office 365 E3 for the past number of years. we would like to configure a windows 2019 essentials server locally for file storage and a few shared applications (ie quickbooks multi-user).
is there a process to pull the user information from azure active directory to the local server? any advice is greatly appreciated.
thank you!!
If my understanding is correct, you really want is to be able to grant admin rights to your Azure AD users and allow them to login to the server with their regular Azure AD credentials.
If yes, then most optimum way of doing is to have on prem AD and have you user synced up from Azure AD to local AD. Azure AD Connect comes pretty handy in this scenario.
You can also take a look at Azure AD DS, Azure Active Directory Domain Services (Azure AD DS) provides managed domain services such as domain join, group policy, lightweight directory access protocol (LDAP), and Kerberos / NTLM authentication that is fully compatible with Windows Server Active Directory. You use these domain services without the need to deploy, manage, and patch domain controllers in the cloud. Azure AD DS integrates with your existing Azure AD tenant, which makes it possible for users to sign in using their existing credentials.
https://learn.microsoft.com/en-us/azure/active-directory-domain-services/overview
Check this link as well for additional reference:
https://serverfault.com/questions/808047/how-to-manage-on-premise-servers-using-azure-ad-credentials
Hope it helps.

Can a local/on premises domain Trust Azure AD?

I am not sure this is possible, but can Azure AD be trusted by a local on-premises domain?
I can see plenty of information on extending the local domain into Azure, but my requirement is more of less the reverse of this.
Ideally I would like the local domain to trust Azure AD, but as an alternative
could Azure AD DS be used to extend Azure AD into an Azure AD DS domain and then have a two way trust with the local domain?
I am not sure this is possible, but can Azure AD be trusted by a local
on-premises domain?
As I know, there is no way to make Azure AD be trusted by a local on-premise domain.
Azure AD is used for authentication for Internet-based services such as Office 365 and Azure, as well as much more, including Facebook and thousands of other services that are already federated with Azure AD (which mean they trust Azure AD without you having to do anything other than enable that application or service to be used by your users).
Your on-premises Active Directory can be synced to Azure AD by using Azure AD Connect (including password sync) and federation. This allows users on their corporate assets to log on with their AD account and when they access Internet services, such as Office 365, authentication with Azure AD just happens seamlessly via the federation, allowing access to all the different services that Azure AD is federated with.
Azure AD Domain Services provides managed domain services such as domain join, group policy, LDAP, Kerberos/NTLM authentication that are fully compatible with Windows Server Active Directory. You can consume these domain services without the need for you to deploy, manage, and patch domain controllers in the cloud. Azure AD Domain Services integrates with your existing Azure AD tenant, thus making it possible for users to log in using their corporate credentials.

Resources