Hi VesaJuvonen /PoojaG . Providing some hopefully useful feedback.
Firstly, it looks great, and I can see you've put a massive amount of work into this. I'm sure it will be a nice addition for many of your customers. However, we are not ready for this now. Questions/notes below:
- Will there be an option for us to disable this across our tenant until we are ready to enable it? Please say yes (we're still desperately working on getting Site branding disabled as it goes completely against our brand strategy).
- If just using the out-of-the-box Cards, there is not a lot of functionality we can get within the Card itself unless we extend them with SPFx. However, our company isn't using any SPFx and isn't set up for it (governance, development, support, etc.). Also, if we were going to use SPFx then we'd create Webparts instead of Adaptive Cards as we get full design and extensibility (Adaptive Cards by nature are structure and content only - no - or limited - design aspects).
- Users will also start to use the Adaptive Cards Designer to generate their JSON they need to add back into the Cards. We don't have support in place to manage this aspect either when the Cards don't work as expected, or users ask for help designing them.
- After creating a Site dashboard, are you able to delete it? I see that you can turn it on/off which might be ok instead of deletion.
- For users to start using the dynamic connections (Graph/SP REST) do we need to enable this at the tenant level, or can it be site by site (hoping the later). If only tenant wide setting, then that's an issue for us.
- SP REST API is limited to the current site which severely limits its usefulness. A lot of the data we would look to retrieve would potentially live on other sites. I know we can use the Graph connector, but limited data is available (think Site/Web properties, etc.). Is there anything on the roadmap to allow SP REST API to go across other sites?
- Who can create and manage dashboards - only owners, or anyone with Edit rights?
- Who can add the dashboard webpart to the site?
- Who can create Cards? If it's only owners and they want people to create Cards for them, they will have to make those users owners, which is a governance/security concern (access to everything). Will there be a new role available for this, or how will it work?
- I saw you had max number of Cards displayed = 5 (quite limited) - any reason for just that many?
- When will it be in GA (or released as part of TAP)? You mentioned in the video it would be completed by the end of May, but the Microsoft Roadmap still says In Development?
- Approvals: Most of our approvals are within custom Power Platform environments (not the default one) so none of those approvals show up as they have their own Dataverse environment and associated Approvals tables. Anything on the roadmap to fix this in general where we can have a global view of all approvals across all Power Platform environments?
For Viva Connections (in relation to the Dashboard) in Microsoft Teams:
- Can you allow us to remove the Viva Connections Footer that has links to your Viva Microsoft Site and the other Viva features? It seems a bit strange that we're forced to keep this as our footer.
- Can you allow us to remove the dropdown showing the other Viva features? We don't want our users going directly to Viva Learning as we have a dedicated Learning site they should be directed to.
- The Welcome [name] is always black text. I added a background image that was quite dark, and I almost couldn't read the Welcome message. It would be nice if it picked up the contrast of the image and rendered appropriately (light/dark).
- The Navigation allows you to select links from the Global Navigation but doesn't retain any of the hierarchy that we have in our Global Navigation. It would be nice to somehow replicate this within the Microsoft Teams view. I'm not sure if it has any sort of syncing either - if we select a link from our Global Navigation then we update the Global Navigation, will that change reflect in Microsoft Teams?
Sorry for the long feedback - hopefully, it helps you (Microsoft) and your customers when looking at these features.