We are designing a Dynamics 365 solution for a customer that already have an existing tenant with an Azure AD that uses federation through AD-FS.
We would like to design a solution using a separate tenant and Azure AD with Dynamics 365 (online). The idea would then be that we should invite users from their tenant to "our" tenant using Azure AD B2B.
We've found that there are limitations using Unified Service Desk client and using the users own email, using this approach. Are there other known limitations?
Could this be solved in a better way, still using two separate tenants?
Microsoft states that the following features are not supported when using Azure B2B together with Dynamics 365:
Unified Service Desk client
Dynamics 365 App for Outlook
Invited users cannot perform email activity using their own email address
Office 365 Groups
Read details at link
Related
We have multiple domains on our Office 365 tenant. I would like to know if it is possible to use multiple identity providers (e.g. Okta or PingIdentity) within one Office 365 tenant - one identity provider per domain. So, users in DomainA.com would authenticate using Azure AD. And users in DomainB.com would authenticate using Okta.
Has anyone tried or had any experience doing this?
Yes, it is. You can have a different IdP for each domain mapped to your Office 365 tenant.
Is it mandatory that the tenant has to have Microsoft Office 365? Can we sync our on premise Active Directory to Azure AD using Azure Connect and login to Microsoft Teams using AD credentials?
the Full version of teams requires an office 365 license. as this is an office 365 product.
Without an office 365 license that includes teams. you won't be able to use the full version of teams regardless of AD Account.
So to answer your question. yes it is mandatory to have a o365/teams license in order to use teams.
There is however a free version of teams that you can use, and if your entire tenant in aad doesn't have any office 365 at all, then 'I believe' you can log into / sign up for that free version.
though there are various limitations on that version but if you are just testing it out, or are a small organization, of less than 25 users then you could use it.
I have a scenario that I am hoping someone can assist me with. I have a requirement to build an extranet in SharePoint Online (Office 365).
We have a main Office 365 Tenant. There are 15 member organisations that need access and these DO NOT have Office 365. on premise only.
So I can use Azure B2B to grant access to SharePoint Sites no problems. I need the social aspect and Yammer Fits PERFECTLY but identities are separate.
I can create and External Yammer Network and invite users but obviously these are a separate set of credentials to that of Azure AD.
Has anyone done such a thing and is there a way to grant Azure B2B users access to an external Yammer network?
Yammer should allow you to sync with your Azure Active Directory. This should allow users to have the same logins.
Here is some information I found on this matter:
https://products.office.com/en-gb/yammer/yammer-network-administration
In doing some more testing today, I am finding that when I get an access token for a user that has been added to a tenant via the Azure B2B feature, I cannot access the site content using the Office 365 APIs.
Is there any plan to enable this scenario by RTM for Azure B2B? I'm finding more and more blocking scenarios like this where a user has been granted access to a resource, but access through the Office 365 APIs is not working.
I have the following setup:
Exchange 2013 on-premise with 10 users
AD on-premise
We have Office 365 premium licenses for each person in the company and have an Azure account etc.
I have been tasked with migrating the users to Office365 and also migrating AD
The Exchange Online licenses are not yet active, so currently, there are no user mailboxes on Office365.
We want Azure AD to replace our on-premise AD as at some point, the AD and Exchange servers (on-premise) will be decommissioned.
What path would be the best for me to take to do the migration?
I have read various pages on learn.microsoft.com about AD sync and AD Connect but am not sure whether or not this is the right way to go. the docs all seem to be geared towards companies needing a hybrid setup and we don't want that, ultimately.
Tips and advice will be gratefully welcomed.
Best regards,
Neil.