m365 spo homesite add

[reshmee011]

Usage

m365 spo homesite add

Description

Create a viva connection experience

Options

Option	Description
-h --homeSiteUrl <homeSiteUrl>	The home site url to create a viva connection experience

Examples

Create a viva connection experience

m365 spo homesite add --homeSiteUrl "https://reshmeeauckloo.sharepoint.com/sites/testcomms"

Default properties

• Title
• Url

Additional Info

This is to fix bug #6066 which requires the additional cmdlet to add home site which is separate from the update home site.

After peer review, I am happy to work on it.

[milanholemans]

Hi, @reshmee011, thanks for the issue. A few remarks from my side:

• To me it seems odd that the description tells us we are doing something with Viva Connections, while it's an spo command. Do you think Adds a new site as home site or something like that covers the load?
• For the option, instead of repeating homeSite in the option name, I'd just opt for -u, url <url>.
• Since this is an add command, default properties are not needed. This is only required for list commands.

Other command-related questions:

• Does this mean that we should update the description of the command spo homesite set so that it only updates a home site instead of adding it?
• Should we update spo homesite get and spo homesite remove with a required siteUrl option?

[reshmee011]

@milanholemans : My answers to the questions

• To me it seems odd that the description tells us we are doing something with Viva Connections, while it's an spo command. Do you think Adds a new site as home site or something like that covers the load?

As per Ms documentation from https://learn.microsoft.com/en-us/viva/connections/set-up-admin-center, it's "Create a Connections experience"

For the option, instead of repeating homeSite in the option name, I'd just opt for -u, url . Done
Since this is an add command, default properties are not needed. This is only required for list commands.Done

Other command-related questions:

Does this mean that we should update the description of the command spo homesite set so that it only updates a home site instead of adding it?
We can add the Home Site/Connections Experience as well as setting the properties of the Home Site/Connections Experience

Should we update spo homesite get and spo homesite remove with a required siteUrl option? Yes, we should update them, the endpoints will have to change to ones that can accept the siteUrl parameter.

Documentation how to programmatically manage those viva connection experiences is lacking. I am using the browser's developer tools to identify the endpoints.

[milanholemans]

As per Ms documentation from https://learn.microsoft.com/en-us/viva/connections/set-up-admin-center, it's "Create a Connections experience"

Yeah, we are kinda in a gray area here. Setting up the home site automatically creates a VC experience as well, but in this case that's not really the purpose of the command, but rather a side-effect I guess?

Does this mean that we should update the description of the command spo homesite set so that it only updates a home site instead of adding it? We can add the Home Site/Connections Experience as well as setting the properties of the Home Site/Connections Experience

I didn't notice the other issue you've created, so you can ignore this comment.

Should we update spo homesite get and spo homesite remove with a required siteUrl option? Yes, we should update them, the endpoints will have to change to ones that can accept the siteUrl parameter.

Is it possible for you to specify issues for this as well? We would really appreciate that. Note that these commands should have a required option url, but since CLI is backward compatible until we create a new major version, we'll have to implement is as an optional parameter and show a deprecation warning when someone doesn't provide a URL.

[reshmee011]

Yeah, we are kinda in a gray area here. Setting up the home site automatically creates a VC experience as well, but in this case that's not really the purpose of the command, but rather a side-effect I guess?

We can leave it Add a Home Site.

Is it possible for you to specify issues for this as well? We would really appreciate that. Note that these commands should have a required option url, but since CLI is backward compatible until we create a new major version, we'll have to implement is as an optional parameter and show a deprecation warning when someone doesn't provide a URL.

I have raised issues

• m365 spo homesite remove fails #6491 to fix m365 spo homesite get
• m365 spo homesite get requires additional siteUrl parameter for multiple home sites experience #6490 m365 spo homesite remove
• m365 spo homesite list #6492 m365 spo homesite list