User Profile
WH-808
Copper Contributor
Joined Nov 17, 2017
User Widgets
Recent Discussions
Re: Sharepoint Subscription Edition error anonymous access user profile application
LabTest788 Doesn't seem like a bug, it looks more like use of the service application vs. intent of the service application. I don't believe the user profile service application was intended for use on anonymous sites, but intranet sites and the like that require authentication. I've never used it on an anonymous site and mixing anonymous access and authenticated access on the same web application has generally lead to pain in my SharePoint experiences. You can usually separate the two completely, or a the very least, use separate zones and URLs for each by extending the web application and setting unique authentication methods for each zone, ie, set anonymous on one zone and require authentication on the other. It's probably best to separate them though to keep the service application out of the mix, unless there is a way to use separate service applications per zone now.1.3KViews0likes0CommentsRe: Azure AD Connect and On-Prem ADFS federated with multiple partner organization
I mean federation as defined, which is joining two distinct or disconnected directories. The purpose is so you do not have to create and manage users in the other directory. The user account exists and is maintained in one directory, but can access resources trusted by another directory. You can setup a B2B tenant if you'd like, but that is just one way to accomplish it. You are correct that a user object has to exist in the Azure AD tenant to login to O365, that is what the invite as external user from another Azure AD tenant option does. This only makes the user available to be granted access to applications under the tenant, but their user account still exists and is maintained in the other tenant.8.6KViews1like0CommentsRe: Azure AD Connect and On-Prem ADFS federated with multiple partner organization
I think you might be mixing up federation with sync. You can't sync a domain to more than one tenant but you can absolutely federate with other directories. If they are in another Azure tenant, you have two options, invite them as external users to your tenant or setup federation between two tenants using custom policies. If you don't mind external users in your directory, then inviting them as external users is by far the easiest of the two options.8.6KViews0likes2CommentsRe: Azure AD Connect and On-Prem ADFS federated with multiple partner organization
I'd assume they wouldn't want them using a Microsoft account for account management purposes. You can signup for a Microsoft account with any email address. If they do it with their work email address, two things would happen that would be issues with a lot of organizations. 1. It would be a separate account with a separate password. 2. If they left the partner company, they would still be able to login with the Microsoft account after the company partner account is deactivated or password changed. The partner would need their own Azure AD with on-prem accounts synced or their own ADFS and you would federate your Azure AD with that.8.7KViews2likes4CommentsRe: Azure AD Connect and On-Prem ADFS federated with multiple partner organization
Easiest implementation would be your partners also sync their users to Azure AD. Then you can invite them as a guest to your tenant and then they will be available to add a users in Office 365.8.7KViews0likes0Comments
Recent Blog Articles
No content to show