Background
Your IFD URL is always going to be OrgUniqueName.domain.com. The domain is setup when you first setup IFD and the Unique Org Name is setup when you first create the Org. If you want to see your unique org name then you can goto Deployment Manager and look in the "Name" column.
When ADFS asks CRM for its endpoints (Relying Party Identifiers), CRM will include an endpoint for each Org.
Prerequisites
You can use any sub domain URL (*.mycompany.com) provided that:
- There is no other CRM org in the same instance with the same full URL (same unique name as the sub domain)
- It is under the same domain as the ticket service (STS). So for example you can’t use auth.mycompany.com for the STS and crm.myothercompany.com for CRM. At least not without some ADFS metadata tricks.
- The name can be cleanly mapped to a single network endpoint within your network. Simply put, it can’t already be mapped to something.
- You have a covering SSL cert (either a cert for the exact URL or a wildcard certificate).
Changing the Org Unique Name
In order to change the org unique name, you need to re-import the org under a new name. Here are the steps involved:
- Backup the organization database (OrgName_MSCRM)
- Disable the org in Deployment Manager
- Delete the org in Deployment Manager
- Optional but recommended: Delete the org database (OrgName_MSCRM) and restore it with the new org name (NewOrgName_MSCRM). You don’t have to do this but it would keep the org name and database name in line
- Import the org and give it the new name
- Go into the ADFS MMC console, right-click on the Relying Party Trust and choose “Update from Federation Metadata. This causes ADFS to go ask CRM for the endpoints again and CRM will answer with all enabled orgs.
