My boss purchased Microsoft 365 which came in three products. He now challenged me to design a management system, like an employee self-service portal. I am hereby looking for advice on where to start or which product to use, since I am new to this.
I have tried a bit of research and I came across the Sharepoint platform which can be used to create workflows and automate tasks. Is this the right way forward or there is a better and standard way to do it? Please somebody advise me.
Yes, you are on the right track if your goal is to create an employee portal. SharePoint and Azure Active Directory are the right services to start with. There is no best practice per say since it is all code and you could even build your own .NET app from scratch if you wanted to do that, but SharePoint is useful because it can give you some frameworks for getting something like an employee self-service portal set up quickly.
There are some good tutorials out there for this already:
https://www.youtube.com/watch?v=1NX0oh3VSNU
https://resources.techcommunity.microsoft.com/resources/build-modern-intranet-on-sharepoint-office-365/
This one even has some best practices for design choices:
https://blog.mydock365.com/employee-portal-design-sharepoint-intranet/
Hope this helps!
I would encourage you to explore the training portal for Microsoft 365 and SharePoint specifically:
Here is a link to the free SharePoint training resources offered there:
Microsoft Support: SharePoint video training
This site also offers some fantastic infographics and cheat-sheets for SharePoint:
How to customize your SharePoint website
Office cheat sheets: SharePoint Online
Check out the SharePoint Look Book:
SharePoint Look Book
Related
I have a sharepoint Online Communication site that I'd like to migrate to another tenant.
Is there an easy way to achieve that?
Thanks.
You can have a try to "Save site as template" feature on the feature, see this: https://expert-advice.org/office365/migrate-sharepoint-online-different-sharepoint-onlineoffice-365-tenants/. To migrate a SharePoint Online site collection, it is recommended to consider using third party migration tools.
My company switched from an onsite SharePoint 2013 to SharePoint Online.
I had some pages that consisted of multiple web parts, including the filter web parts.
I've rebuilt these pages in Sharepoint Online, but none of the filter web parts are available.
Every list is set to use classic experience - except the site itself, which I do not have control over.
According to IT support these specific filter web parts are simply not available in SharePoint Online, and therefore they can't help me.
I honestly don't trust that answer completely, which is why I'm asking here ;-)
So:
Can the filter web parts be made available for classic view in Sharepoint Online?
Suggestion on what would need to be configured in order for these to be made available?
Possible links to official Microsoft documentation?
Thanks :-)
Per my test, the filter web parts are available in SharePoint Online. As the below picture shows:
You could donot have access to the web part gallery. Ask the site admin to give your access to the web part gallery: please go to site settings-> Web parts, grant the user access to the library.
I'm looking at upgrading my current TFS instance and planning to copy and restore databases as per Microsofts Advanced Upgrade which means I am pretty much installing the new product from scratch and restoring the databases then running a migration tool.
I see in the installation notes that you can integrate SharePoint with it as an optional extra. Why would I do this? Is the idea to store project documentation in a SharePoint Document library per project and be able to link to that content rather than as an attachment to the Backlog Items and Bugs in TFS?
I'm having trouble finding any documentation of team workflows with SharePoint and TFS and I suspect that its because no one really does it.
More importantly would SharePoint integration impede future product upgrades or moving to Visual Studio Online?
In my eyes, SharePoint as a TFS portal has become much less desirable due to the improvements in Team Web Access (eg Charting) but it still has some uses.
With the integration enabled, you will see a Documents tab in Team Explorer which will take you to the dedicated SharePoint Portal (created when you create the TFS Team Project) where all your documentation can be stored. Of course without SharePoint integration you can still happily link Work Items to documents in SharePoint, you just don't have a dedicated portal created for you.
If you are using one of the MSF process templates then some useful documents are created for you on SharePoint when you create the Team Project (xlsx reports etc). However, if you are using the much better VS Scrum template then no documents are created even if you have SharePoint integration enabled.
If you are using the Enterprise edition of SharePoint then you get some good dashboards (bugs, code quality etc.) and you can also publish your custom excel reports easily. This functionality requires Excel Services and so is not available in the standard edition (there are some dashboards created but they aren't that useful).
Share information using the project portal
https://msdn.microsoft.com/en-us/library/ms242883.aspx
Your team can use the SharePoint portal to share information in the following ways:
Share data contained in reports or dashboards
Share team progress using predefined or customized dashboards.
Share documents, files, images.
Share team knowledge and processes using the SharePoint wiki.
Reference process guidance for select team project artifacts.
If you want to add a portal to an existing project:
Configure or add a project portal
https://msdn.microsoft.com/en-us/library/ms242865.aspx
I do not know clearly the merits and demerits of SPS and SPT. I was searching in google too for the past one week, but could not. Can anyone help?
This post will give you the correct terminology to use for the different editions and versions :-
SharePoint Versions through the ages – Confused?
To compare the features of different versions :-
SharePoint 2010 - Foundation / Server / Enterprise
SharePoint 2007 - WSS 3.0 / MOSS 2007
SharePoint 2003/2001 - Really? Time to upgrade ;)
I know only the merits of SPS and STS, so i have given it below. Let me give you some other time demerits. Let you check the merits of it here. Let me know for any clarifications.
SharePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial.
I have a WSS SharePoint site that i need to deploy and publish to that Users will be able to access it through the internet.
I know this is possible, but how do i go about getting this done?
Does anyone have some good articles?
Kind Regards
Etienne
From Microsoft Team Blog, essentially a page linking to relevant articles.
You can also download the SharePoint Planning Services Starter Kit