How to use the Microsoft Knowledge Base in Service Manager

La Microsoft knowledge base and Service Manager knowledge articles They have become an essential tool for any IT department that wants to work in an organized and efficient manner with fewer recurring issues. When used effectively, this solutions database allows both analysts and end users to resolve questions and errors without having to constantly open new tickets.

In this article you will learn How to create, search, and link knowledge articles in Service ManagerFollowing the best practices used by Microsoft in its own Knowledge Base, you'll see step-by-step how to properly document problems, how to make it easy for users to find information, and how to link each solution to incidents and change requests so that everything is perfectly tracked.

What is the Microsoft knowledge base and how does it fit into Service Manager?

The main idea of ​​a knowledge base is that Knowledge is not lost every time someone solves a problemInstead of relying on the technician's memory, the solution is documented in an article that can then be consulted again and again, both by other analysts and by the organization's own employees.

In the case of Service Manager, the Knowledge articles are integrated with the working elements (incidents, change requests, etc.). This allows the analyst, when investigating a problem, to quickly search for related articles, apply them, and also keep a record of what knowledge was used to solve each case.

One of the great advantages is that Any employee can search and view knowledge articlesAnd in many scenarios, they can also create them, provided they have the appropriate permissions. This promotes self-service: users can find solutions to common IT problems themselves before opening a new ticket, reducing the workload of the support department.

In addition, Service Manager is designed for support analysts directly link knowledge articles to incidents or change requestsThis generates a clear history: what documentation has been used, what procedures have been followed, and what external references have been consulted.

How to create a knowledge article in Service Manager

Creating a good knowledge article is not just about writing a few lines; it's fundamental structure it well so that it is easy to find and understandThe following details the typical procedure for generating a new article from the Service Manager console, using a common example: explaining how to get the latest Service Pack or cumulative update for Windows 10.

The goal of this process is for the result to be a reusable resource, where title, description, keywords, owner, category, and external and internal content are properly defined. This facilitates both the maintenance of the knowledge base and its use in day-to-day support.

To create a knowledge article in Service Manager, you can follow these basic steps, adapting the content to your own IT scenario:

1. Open the Service Manager console and enter the area of LibraryThis is the section where all management of shared elements is centralized, including the knowledge component.

2. In the library navigation panel, expands the Knowledge node and select the view All knowledge articles to work on the complete list of existing documentation.

3. In the task pane, usually located on the right, locate the section Knowledge and choose the option Create knowledge articleThis opens the specific form for defining a new record.

4. In the General In the article form, within the knowledge information area, it is important to complete the key fields carefully:

   1. In the countryside TitleEnter a clear, direct, and easy-to-find name. For example, you could use something like How to download and install the latest Windows 10 Service Pack, or any phrase that unambiguously describes the content.

   2. In the description box, write a short but informative text explaining the purpose of the article. Something like this: This procedure details the steps necessary to understand the problem and apply the fix using the latest service pack usually works very well.

5. On the same form, expand the Classification sectionThis part is critical for your articles to be discoverable through subsequent searches:

   1. In the countryside KeywordsIntroduce terms that describe the content and that a user might type when searching. They are usually separated by semicolons, for example: Windows;Service Pack;Update;Windows 10The more representative they are, the easier it will be for the article to appear in searches.

   2. En Owner of the knowledge articleSelect the person or group responsible for keeping the content updated. This could be, for example, the lead technician for the Windows platform or the person in charge of the systems area.

   3. On the list CategoryChoose a classification consistent with your organization's taxonomy: Software, Hardware, Socialetc. An article about Windows 10 would fit, for example, in the Software category.

6. Then Open the External Content sectionHere you specify the official references or external sources that support the information in the article:

   In the countryside Url addressEnter the source website if you know it. This could be a link to Microsoft's own Knowledge Base, for example: https://support.microsoft.com/kb/935791 or another URL that contains the official documentation related to the problem you are addressing.

7. Next, expand the area of Internal contentThis section outlines the guide adapted to your company's specific situation, explaining how to apply the general information to your particular environment.

   In the internal content text box you can write, for example: Access the provided URL to view the official Microsoft instructions and, once reviewed, follow the procedure defined by IT in this organization to deploy the latest Windows 10 service pack.Here you can include specific steps, internal routes, corporate deployment tools, etc.

8. Lastly, select Accept to save the new knowledge article. From that moment on, the record will be available for searches and to link to incidents and change requests.

Once saved, it's a good idea to do a quick check to make sure that The article has been created successfully and appears in the appropriate views.The first check is usually simply to verify that the new record is on the list of All knowledge articles inside the console.

How to verify that the knowledge article has been created correctly

After creating an article, it's a good idea to perform a quick validation to avoid errors such as misspelled titles, incorrect categories, or articles that are not displayed where they should beThis will save you from later problems when analysts or users try to locate information that "theoretically" already exists.

The first check consists of reviewing, within the corresponding view, that The new article appears in the All Knowledge Articles panelIf you find it there, you can open it, review the entered fields and, if necessary, correct or complete the data.

It is recommended that, in that initial review, Try also a quick search using some of the keywords that you have defined. This confirms that indexing and filtering are working as expected and that the content can be easily located using the integrated search engine.

How to search for knowledge articles in Service Manager

One of the great strengths of the Knowledge Base integrated into Service Manager is that it allows you to perform full-text searches across different fields of the articleNot only is the title analyzed, but also other relevant sections, which significantly increases the likelihood of finding useful information even when the user does not know the exact title.

When you launch a search, Service Manager examines, among others, the following fields defined in the knowledge form:

• Title, where the descriptive name of the article is included.

• Descriptionwhich usually summarizes the problem and the solution.

• Comments, area where additional notes can be recorded.

• Keywords, which serve as labels to refine the results.

• External URLwhich sometimes also contributes significant terms.

• Internal content, which details how to apply the solution in the organization's environment.

• Analyst content, section designed for more technical information intended for support staff.

Once the search is executed, the system displays those knowledge entries that They match the entered textThe results typically highlight fields such as Title, the End-user content and the Analyst contentso that the technician can quickly assess whether the found item is relevant.

If you need to review the full content, you can use the option Open article to view external contentThis allows you to access all stored information, including links to Microsoft online documentation or other official sources that you have referenced in the external URL section.

It is important to keep in mind that, when performing a search, The entered string must exist exactly as is in one of the indexed fieldsFor example, if you type "Windows 10" in quotation marks, the system will try to find that exact combination within the title, description, content, keywords, or other relevant fields of the article.

Search for knowledge articles from the main console

The most common way to locate documentation is to use the Service Manager console general search boxFrom there, you can filter by object type and focus exclusively on knowledge articles, without mixing the results with incidents or other work items.

To search for a knowledge article from the console, the procedure is usually very simple and straightforward, even for analysts who are new to the tool. The key is in Choose the right search terms and select the correct object type..

1. At the top of the Service Manager console, locate the search box and enter a keyword, term, or phrase that makes sense in relation to the problem you want to solve. For example, you could write Windows 10 if you are dealing with an issue with that operating system.

2. To the right of the search box, click the arrow that shows the different types of objects available. In the list, select the option Knowledge to indicate that you only want results from the knowledge base and not from other areas.

After launching the search, the form Knowledge search It will only display articles that match the entered term. From that screen, the analyst can open the articles, read their content, review external links, and assess whether the information is relevant to the case they are working on.

Search for knowledge articles from an incident or change request

In addition to generic searches, Service Manager allows Consult the knowledge base directly from an incident form or a change requestThis is very practical because it reduces clicks and keeps the analyst focused on the specific context of the incident they are managing.

Before initiating a search from the incident or change form, it is important that the work item is saved at least onceOtherwise, some linking and recording operations of associated knowledge may not be available or may not be correctly reflected in the system.

When you have an incident or change request form open, the steps to query the Knowledge Base are similar to those in the general console, but integrated into the form you are working on.

1. With the incident or change request form open, go to the dashboard Tasks which appears on one of the sides and selects the option Search for knowledge articlesThis will open the specific search form for the knowledge base.

2. In the form of Knowledge search, enter in the box Search The term or set of words related to the problem. You could write, for example, Windows 10 if you are working with incidents in that environment.

3. Press on Ir or by clicking the corresponding button to start the search. The system will return a list of articles matching the text you entered, and from that same interface, you can open them, review them, and even link them to the work item if they are relevant.

This way of working allows that Each incident or change request is associated with the documentation that was used for its resolution, something very useful for internal audits, trend analysis and continuous improvement of support procedures.

Link knowledge articles to incidents and change requests

One of the key features of Service Manager is the ability to formally link a knowledge item to an incident or a change requestThis link reflects that this specific document has served as a guide or reference to resolve the issue or manage the modification.

In addition to serving as historical documentation, this relationship facilitates future reference. Analysts can review which solutions have worked best for each type of problem. If it is detected that the same item is used repeatedly for a particular error, it may be a sign that it is advisable to automate the process or even improve the affected product.

To perform this linking from the Service Manager console, you can follow a sequence of steps very similar to the one used when searching for items, but adding the final association with the work item.

1. In the Service Manager console, type the following in the search box: keyword or term that best describes the problem or solution you are looking for, for example Windows 10 or the name of the affected application.

2. As in other cases, use the arrow to the right of the search box to choose the object type and select Knowledge to focus exclusively on the knowledge base articles.

3. the form of Knowledge search It will display all items that match the specified search criteria. Review the list and click on the specific item you want to associate.

4. With the selected item, use the option Link toThis will open a dialog box where you can specify what type of object you want to link the knowledge to.

5. In the window Select objects, within the section Filter by classChoose whether the partnership will be with a Accident or with Change Requestdepending on the case you are handling.

6. Within the same window, locate and select the specific incident or change request you want to associate the article with, and then click on Accept to confirm the selection.

7. Service Manager usually displays an informational message confirming that the linking was successful. Review the notification and click on Accept to close it.

8. Finally, in the form of Knowledge search, click on CLOSE to return to your normal workflow within the console.

Thanks to this procedure, the system maintains an explicit relationship between documented knowledge and real-world cases where it has been appliedThis adds significant value both for the subsequent analysis of incidents and for the training of new technicians.

Best practices for getting the most out of the Microsoft Knowledge Base

Beyond the specific steps, the key to truly leveraging the knowledge base lies in applying good writing, classification and maintenance practicesAn article with a poor title or lacking useful keywords can go unnoticed, no matter how good the solution it contains may be.

It is very useful to define some internal templates for knowledge articlesThese documentation should always include sections such as problem description, affected environment, troubleshooting steps, potential additional errors, and final verification. This helps ensure that all technicians document in the same way and facilitates later review.

Another key point is that there is a clearly assigned owner for each itemThat person or group will be responsible for periodically checking that the information is still valid, that the external links have not become obsolete, and that the procedures are in line with the current infrastructure.

It is also advisable to encourage analysts to incorporate keywords in the language that users actually useIt's not just the technical terminology. If people search for "I can't connect to Wi-Fi" and you've only listed "wireless connectivity problems," the article will be harder to find.

Finally, it's worth periodically reviewing which articles are consulted most frequently and which are hardly used. From this data, one can... improve the most critical content and clean up redundant documentation, keeping the knowledge base as useful and manageable as possible for everyday use.

With careful management of the Microsoft knowledge base and the articles integrated into Service Manager, IT departments can reduce resolution times, avoid repetitive incidents, and offer a much more powerful self-service experience to end users., turning documentation into a true strategic asset and not just a static repository of information.