Closed LuiseFreese closed 2 years ago
@PathToSharePoint - This is your article; just want to keep you in the loop. I say go for it, @LuiseFreese - open source!
Thanks for the list of suggestions @LuiseFreese ! And thx for pinging me @sympmarc , this is a timely topic as it'll be the subject of my presentation tomorrow at the Cal conference.
Certainly the most important point is to turn the list into action, with an actual template. Love the idea! For the record as part of my presentation I'll share a Power BI template and that could be linked too. Click here for the demo.
Sounds good to remove the unused hashtags, I think those were not in my original piece and were added later (maybe more people to ping).
As for #M365PnP and other M365 tags, I ran a poll at the time (Marc was also involved), and the general feedback was that Microsoft365 should be spelled out. Maybe something to revisit... on Twitter! #Microsoft365 is there, actually one of the first on the list.
The list of notable accounts is a tough one, and I think you already called me a nerd on that one ;-) My initial idea was to list all accounts with more than 20,000 followers.
@LuiseFreese follow up on the templates. After doing some work on my Power BI template this week, it's clear that it will require its own repository and page(s) for instructions. Not something that would just fit in the current page. I am open to ideas and suggestions, and to hear what you have in mind for the automate sample. For now my plan is to use my own blog and github repository. btw click here for the latest sample, feedback welcome :-)
I also started looking into the Power Platform Twitter connector. In particular I see that GCC has a specific entry point.
Another path I am exploring is LinkedIn. It is not as popular as Twitter, but being a Microsoft company it certainly deserves a mention in a page dedicated to social media. I could imagine that eventually each hashtag gets two links, one for Twitter and one for LinkedIn (hopefully the hashtags are the same!).
Just making a note that Viva needs to be added too. There seems to be a twitter account https://twitter.com/MicrosoftViva but it is currently protected. As for the hashtags, there is no clear favorite yet between #MicrosoftViva and #MSFTViva. Also, there might be subsets (Topics, etc.).
@PathToSharePoint - @jeffteper made it official on Twitter. It's #MSFTViva.
@sympmarc so #MSFTViva it is, I'd love to hear the rationale here. It seems to me that the rule so far was to NOT abbreviate Microsoft.
I have published my Power BI report for Twitter. I don't want to force it on everybody, so I'll wait to hear if it's worth including in the article. For the record, I'll use it in March to track MS Ignite news. This is also the topic of my upcoming speaking engagement at the Scottish Summit, so hopefully I'll get some more feedback soon.
Next, I'll try to put together a Power Automate template. I guess we actually need two as the GCC connector is different.
Hey, if Jeff says it's #MSFTViva, then that's what it is!
I'm not sure about your Power BI report. It seems that using lists or steams in something like HootSuite give people a way to customize their own Twitter feeds.
@sympmarc good call, and maybe a third party tool like HootSuite is what we could recommend instead of - or in addition to - Power BI or Power Automate.
I am not using HootSuite myself so I'll need to give it a try (or try the Twitter homegrown tool some people have mentioned). The idea with a BI report is to answer questions such as:
At least one benefit I see with the Power BI report is that it doesn't require to login to Twitter. It means that it might be more suitable to an enterprise environment, especially if different groups track different topics.
If you'd like to take a quick look at the Power BI report, I published the one from last week. Maybe you would be able to tell quickly if HootSuite gives you similar information.
I worked with Twitter Connector in Power Apps and in Power Automate, but both Connections required a twitter user as -connection. What do you mean by "doesn't require to login to Twitter" ?
Sorry, my comment was about the Power BI report specifically. It uses a "developer token" to authenticate to the Twitter API, which is different from having a Twitter user account. I have posted more details with the template instructions.
I have corrected my previous post.
💡💡💡 - thank you!
@sympmarc after reviewing the HootSuite offer, the analytics plan doesn't come cheap. So I wouldn't feel comfortable recommending it. On the other hand, a Power BI desktop template is free, and it's a good learning experience when you work with MSFT365
Thoughts? I'll keep looking for other Twitter apps.
@LuiseFreese @sympmarc I just posted a pull request that addresses some of the issues:
@sympmarc I reviewed a couple analytics tools but couldn't find anything interesting AND free. A limited but fun one to try is foller.me. Twitter also has its own https://analytics.twitter.com . For both, analytics are centered on the username, not the topics.
@PathToSharePoint - I hadn't looked at the contents of your PowerBI report when I made my comment above. You're right: third party tools which offer stats like that cost money. But isn't PowerBI itself costly?
Plus, in my mind, the use case for most people is to follow the hashtags on Twitter or LinkedIn or whatever so they can read what's going on. I don't think the "most popular hashtags" type of stats serve that purpose. Or am I missing something in your intent?
It does seem useful to check out the most popular tweets in retrospect. I wonder if focusing on that and making something available in the context of the docs is even possible.
@sympmarc thanks for the feedback! That's why I said I didn't want to force the tool on everybody, I want it to make sense.
To address some of your points:
@sympmarc @LuiseFreese now that the immediate issues have been addressed, would it make sense to move this thread - or at least the part that is still relevant - to discussions?
yes good idea!
There hasn't been much progress on this thread in the past months.
To wrap this up, I would suggest to remove the reference to Power Automate from the article. I am not sure where it came from (could be me...). Personally I am not a fan of promoting Power Automate as copy/paste tool.
As for the notable twitter accounts, maybe that section should be removed too, rather than opening a can of worms. The official accounts listed in the post are already a good reference.
If you think there should be changes, feel free to do a PR.
I'll definitely do a PR. I just wanted to make sure we, and the OP in particular, are on the same page. It's a community endeavor!
I'm fine with that, as already expressed here: https://github.com/MicrosoftDocs/microsoft-365-community/issues/399#issuecomment-785284583
:-)
Article issue
The article Follow Microsoft 365 on Social Media needs some updates and improvements:
Happy to fix that :-)