To update an organization to have Microsoft as a Single Sign-On (SSO) provider, you need to follow several steps: 1. Configure Microsoft as a Social Sign-in Provider: You need to have an Azure account with an active subscription. Follow the steps outlined in the [Ory documentation](https://www.ory.sh/docs/kratos/social-signin/microsoft) to add Microsoft as a social sign-in provider for your project using the Ory Console. This involves registering a new application on Azure, copying the Application (client) ID and Directory (tenant) ID from Azure to the Ory Console, and creating a new client secret. 2. Select a Tenant: When adding Microsoft as a social sign-in provider, you can define which user groups can sign in and sign up with Microsoft by setting the Tenant field. You can either authenticate users that belong to a specific organization (Azure Active Directory) or authenticate users with Microsoft accounts that are not limited to a specific organization. More details can be found in the [Ory documentation](https://www.ory.sh/docs/kratos/social-signin/microsoft#selecting-a-tenant). 3. Data Mapping: Create a Jsonnet code snippet to map the desired claims to the Ory Identity schema. Encode the Jsonnet snippet with Base64 or host it under a URL accessible to Ory Network. Add the social sign-in provider configuration to the downloaded config. Update the Ory Identities configuration using the file you worked with. More details can be found in the [Ory documentation](https://www.ory.sh/docs/kratos/social-signin/microsoft#data-mapping). 4. Update the Organization: Use the

ory update organization

command to update the organization with the given ID. You can specify the project ID, a list of domains, and the label of the organization. More details can be found in the [Ory documentation](https://www.ory.sh/docs/cli/ory-update-organization#ory-update-organization). Please note that to perform the update operation, you must be authenticated by means of the

oryNetworkCookie

method as mentioned in the [Ory API Reference](https://www.ory.sh/docs/reference/api).

The Ory Network configuration file is used to specify various settings for your Ory project. Here's an example of how you might structure this file:

json {     "services": {       "identity": {         "config": {           "courier": {             "smtp": {               "from_name": "My Custom E-Mail Name"             }           }         }       }     }   }

In this example, the configuration file is used to change the name of the email sender for recovery and verification emails. The

"services"

key contains configurations for different Ory services. In this case, it contains configuration for the

"identity"

service. The

"courier"

key is used to configure the email courier, and the

"smtp"

key is used to configure the SMTP server settings. The

"from_name"

key is used to specify the name of the email sender. You can apply this configuration to your project using the Ory CLI with the following command:

bash ory update project <your-project-id> --file config.json

Replace

<your-project-id>

with the ID of your project. This is just an example. The actual configuration file for your project may contain different keys depending on the specific requirements of your project. You can find more information about the configuration options in the [Ory documentation](https://www.ory.sh/docs/guides/cli/config-with-cli).