Does PnP Core .NET Library support authentication against SharePoint Tenants with cutom host names?

%3CLINGO-SUB%20id%3D%22lingo-sub-1194724%22%20slang%3D%22en-US%22%3EDoes%20PnP%20Core%20.NET%20Library%20support%20authentication%20against%20SharePoint%20Tenants%20with%20cutom%20host%20names%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1194724%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20all%20probably%20know%20that%20a%20typical%20SharePoint%20URL%20looks%20like%20the%20following%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fcompany.sharepoint.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcompany.sharepoint.com%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fcompany-admin.sharepoint.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcompany-admin.sharepoint.com%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWell%2C%20I%20work%20for%20a%20client%20that%20somehow%20persuaded%20Microsoft%20to%20get%20a%20custom%20URL.%20so%20the%20URLs%20look%20like%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fo365admin.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fo365admin.com%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fteams.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.com%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EActual%20host%20names%20changed%2C%20but%20you%20get%20the%20idea.%20So%2C%20these%20names%20don't%20have%20%3CSTRONG%3E.sharepoint.com%3C%2FSTRONG%3E%20in%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20had%20some%20issues%20authentication%20with%20PowerShel%20PnP%20against%20these%20URLs%2C%20one%20of%20our%20colleages%20from%20a%20different%20department%20is%20also%20having%20issues%20authentiating%20using%20PnP%20Core%20.NET%20library.%20I%20can%20share%20the%20errors%20later%2C%20but%20the%20%3CSTRONG%3Ebroader%20question%20is%20this%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EDoes%20%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EPnP%20Core%20Library%3C%2FA%3E%26nbsp%3Bsupport%20authentication%20with%20credentials%20(user%20login%20and%20password)%20against%20SharePoint%20tenants%20with%20tenants%20that%20don't%20have%20%3CSTRONG%3E.sharepoint.com%3C%2FSTRONG%3E%20in%20the%20URL%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20insight%20is%20really%20appreciated!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1194724%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

You all probably know that a typical SharePoint URL looks like the following:

Well, I work for a client that somehow persuaded Microsoft to get a custom URL. so the URLs look like:

Actual host names changed, but you get the idea. So, these names don't have .sharepoint.com in them.

 

We had some issues authentication with PowerShel PnP against these URLs, one of our colleages from a different department is also having issues authentiating using PnP Core .NET library. I can share the errors later, but the broader question is this:

 

Does PnP Core Library support authentication with credentials (user login and password) against SharePoint tenants with tenants that don't have .sharepoint.com in the URL? 

 

Any insight is really appreciated!

 

0 Replies