Microsoft Facebook Messenger

1. Microsoft Facebook Messenger Scam
2. Microsoft Facebook Messenger
3. Facebook Messenger App Microsoft Store

Facebook Workplace is a business-oriented version of Facebook, which allows employees to easily connect and collaborate. It contains live videos, news feeds, groups, messenger. Made for big screens and close connections. Get access to free. texting, and high-quality voice and video chat built specifically for desktop. MADE FOR DESKTOP, MADE FOR YOU Type even faster, multi-task while video chatting so you never miss a moment and stay connected with desktop notifications. SPEND QUALITY TIME IN HIGH QUALITY Host one-on-one meetings or bring the whole group together with free., high-quality voice. Create an account or log into Facebook. Connect with friends, family and other people you know. Share photos and videos, send messages and get updates. Unseen for Facebook Messenger Plus is a small extension that doesn't take up much room, as it only has to block a single line of code to disable read receipts from Facebook. One cool feature of Unseen for Facebook Messenger Plus is the ability to manually mark a message as read, giving you absolute control over who sees when you've read a message. Go big with Messenger. A simple app that lets you text, video chat, and stay close with people you care about. Turn off the light in Dark Mode. Give your eyes some rest with a sleek new look.

Messenger (formerly MSN Messenger Service,^[1].NET Messenger Service and Windows Live Messenger Service) was an instant messaging and presence system developed by Microsoft in 1999 for use with its MSN Messenger software. It was used by instant messaging clients including Windows 8, Windows Live Messenger, Microsoft Messenger for Mac, Outlook.com and Xbox Live. Third-party clients also connected to the service. It communicated using the Microsoft Notification Protocol, a proprietary instant messaging protocol. The service allowed anyone with a Microsoft account to sign in and communicate in real time with other people who were signed in as well.

On 11 January 2013 Microsoft announced that they were retiring the existing Messenger service globally (except for mainland China where Messenger will continue to be available) and replacing it with Skype.^[1]

In April 2013, Microsoft merged the service into Skype network; existing users were able to sign into Skype with their existing accounts and access their contact list. As part of the merger, Skype instant messaging functionality is now running on the backbone of the former Messenger service.^[1]

Background[edit]

Despite multiple name changes to the service and its client software over the years, the Messenger service is often referred to colloquially as 'MSN', due to the history of MSN Messenger. The service itself was known as MSN Messenger Service from 1999 to 2001,^[1] at which time, Microsoft changed its name to .NET Messenger Service and began offering clients that no longer carried the 'MSN' name, such as the Windows Messenger client included with Windows XP, which was originally intended to be a streamlined version of MSN Messenger, free of advertisements and integrated into Windows.^[1]

Nevertheless, the company continued to offer more upgrades to MSN Messenger until the end of 2005, when all previous versions of MSN Messenger and Windows Messenger were superseded by a new program, Windows Live Messenger, as part of Microsoft's launch of its Windows Live online services.^[1]

For several years, the official name for the service remained .NET Messenger Service, as indicated on its official network status web page,^[2] though Microsoft rarely used the name to promote the service. Because the main client used to access the service became known as Windows Live Messenger, Microsoft started referring to the entire service as the Windows Live Messenger Service in its support documentation in the mid-2000s.^[3]

The service can integrate with the Windowsoperating system, automatically and simultaneously signing into the network as the user logs into their Windows account. Organizations can also integrate their Microsoft Office Communications Server and Active Directory with the service. In December 2011, Microsoft released an XMPP interface to the Messenger service.^[4]

As part of a larger effort to rebrand many of its Windows Live services, Microsoft began referring to the service as simply Messenger in 2012.^[5]

Software[edit]

Official clients[edit]

Microsoft offered the following instant messaging clients that connected to the Messenger service:

• Windows 8, includes a built-in Messaging client
• Windows Live Messenger, for users of Windows 7 and previous versions
  • MSN Messenger was the former name of the client from 1999 to 2006
  • Windows Messenger is a scaled-down client that was included with Windows XP in 2001
• Microsoft Messenger for Mac, for users of Mac OS X
• Outlook.com includes web browser-based functionality for instant messaging
  • Hotmail, the predecessor to Outlook.com, includes similar functionality for Messenger
  • Windows Live Web Messenger was a web-based program for use through Internet Explorer
  • MSN Web Messenger was the former name of the web-based client
• Xbox Live includes access to the Messenger service from within the Xbox Dashboard
• Messenger on Windows Phone includes access to the Messenger service from within a phone running Windows Phone^[6]
• Windows Live Messenger for iPhone and iPod Touch includes access to the Messenger service from within an iPhone, iPod Touch or iPad^[6]
• Messenger Play! includes access to the Messenger service from within an Android phone or tablet^[6]
• Windows Live Messenger for Nokia includes access to the Messenger service from within a Nokia phone^[6]
• Windows Live Messenger for BlackBerry includes access to the Messenger service from within a BlackBerry^[6]

Third-party clients[edit]

Additionally, these third-party clients and others were able to access the Messenger service:

• Adium (Mac OS X, GPL)
• aMSN (multi-platform, GPL)
• Ayttm (multi-platform, GPL)
• BitlBee (Windows and Unix-like, GPL)
• CenterIM (cross-platform, GPL)
• emesene (multi-platform, GPL)
• Empathy (Linux GNOME, GPL)
• eBuddy (Web-based and mobile)
• Fire (Mac OS X, GPL)
• XMPP (any client supporting XMPP protocol can use transports to connect to the Messenger service)
• Kopete (Linux KDE, GPL)
• Meebo (Web-based)
• Meetro (multi-platform, proprietary)
• Miranda IM (Windows, GPL)
• Pidgin (formerly Gaim) (multi-platform, GPL)
• tmsnc (multi-platform, text based)
• Trillian (multi-platform, Web, proprietary)
• Yahoo! Messenger (multi-platform, proprietary)

Criticism[edit]

Microsoft Messenger has been criticized^{[by whom?]} for the use of the Microsoft Notification Protocol, which does not provide any encryption. This makes wiretapping personal conversations in Messenger possible if someone intercepts the communication, which is easy in unencrypted public Wi-Fi networks.^{[citation needed]}

See also[edit]

References[edit]

1. ^ ^abcdefMicrosoft Launches MSN Messenger Service
2. ^Check the Microsoft .NET Messenger Service status
3. ^Microsoft Help and Support: Important changes to Windows Live Messenger
4. ^'Anyone can build a Messenger client—with open standards access via XMPP'. Windowsteamblog.com. Retrieved 2013-06-15.
5. ^Messenger service status
6. ^ ^abcdeGet Messenger on your smartphone—it's easy and it's free! Retrieved 7 September 2012

External links[edit]

Your bot can be connected to both Facebook Messenger and Facebook Workplace, so that it can communicate with users on both platforms. The following instructions show how to connect a bot to these two channels.

Note

The Facebook UI may appear slightly different depending on which version you are using.

Connect a bot to Facebook Messenger

To learn more about developing for Facebook Messenger, see the Messenger platform documentation. You may wish to review Facebook's pre-launch guidelines, quick start, and setup guide.

To configure a bot to communicate using Facebook Messenger, enable Facebook Messenger on a Facebook page and then connect the bot.

Copy the Page ID

The bot is accessed through a Facebook Page.

1. Create a new Facebook Page or go to an existing Page.

2. Open the Facebook Page's About page and then copy and save the Page ID.

Create a Facebook app

1. In your browser, navigate to Create a new Facebook App.

2. Enter the name of your app and select Create New Facebook App ID.

3. In the displayed dialog, enter your email address and select Create App ID.

4. Go through the wizard steps.

5. Enter the required check information, then select Skip Quick Start in the upper right.

6. In the left pane of the next displayed window, expand Settings and select Basic.

7. In the right pane, copy and save the App ID and App Secret.

8. In the left pane, under Settings, select Advanced.

9. In the right pane, switch the Allow API Access to App Settings slider to Yes.

10. In the page bottom right, select Save Changes.

Enable Messenger

1. In the left pane, select Dashboard.

2. In the right pane, scroll down to the Messenger box and select Set Up. The Messenger entry is displayed under the PRODUCTS section in the left pane.

Add pages and generate tokens

1. In the left pane, under the Messenger entry, select Settings.

2. In the right pane, scroll down to Access Tokens and select Add or Remove Pages.

3. From the list that comes up in the next window, choose the pages you want to use with the app.

4. Select Done.

5. To generate a token for this page, select Generate Token.

Enable webhooks

In order to send messages and other events from your bot to Facebook Messenger, you must enable webhooks integration. Leave the Facebook setting steps pending. You'll update them later.

1. In your browser open a new window and navigate to the Azure portal.

2. In the Resource list, select on the bot resource registration and in the related blade select Channels.

3. In the right pane, select the Facebook icon.

4. In the wizard enter the Facebook information stored in the previous steps. If the information is correct, at the bottom of the wizard, you should see the callback URL and the verify token. Copy and store them.

5. Select Save.

6. Go back to the Facebook settings to finish up the configuration process.

7. Enter the callback URL and verify token values that you collected from the Azure portal.

8. In the Webhooks configuration section, enable the following subscriptions:message_deliveries, messages, messaging_options, and messaging_postbacks.

Submit for review

Facebook requires a Privacy Policy URL and Terms of Service URL on its basic app settings page. The Code of Conduct page contains third party resource links to help create a privacy policy. The Terms of Use page contains sample terms to help create an appropriate Terms of Service document.

After the bot is finished, Facebook has its own review process for apps that are published to Messenger. The bot will be tested to ensure it's compliant with Facebook's Platform Policies.

Make the App public and publish the Page

Note

Until an app is published, it is in Development Mode. Plugin and API functionality will only work for admins, developers, and testers.

After the review is successful, in the App Dashboard under App Review, set the app to Public.Ensure that the Facebook Page associated with this bot is published. Status appears in Pages settings.

Connect a bot to Facebook Workplace

Note

On December 16, 2019, Workplace by Facebook changed its security model for custom integrations. Prior integrations built using Microsoft Bot Framework v4 need to be updated to use the Bot Framework Facebook adapters per the instructions below prior to February 28, 2020.

Facebook will only consider integrations with limited access to Workplace data (low sensitivity permissions) eligible for continued use until December 31, 2020 if such integrations have completed and passed Security RFI and if the developer reaches out before January 15, 2020 via Direct Support to request continued use of the app.

Bot Framework adapters are available for JavaScript/Node.js and C#/.NET bots.

Facebook Workplace is a business-oriented version of Facebook, which allows employees to easily connect and collaborate. It contains live videos, news feeds, groups, messenger, reactions, search, and trending posts. It also supports:

• Analytics and integrations. A dashboard with analytics, integration, single sign-on, and identity providers that companies use to integrate Workplace with their existing IT systems.
• Multi-company groups. Shared spaces in which employees from different organizations can work together and collaborate.

See the Workplace Help Center to learn more about Facebook Workplace and Workplace Developer Documentation for guidelines about developing for Facebook Workplace.

To use Facebook Workplace with your bot, you must create a Workplace account and a custom integration to connect the bot.

Create a Workplace Premium account

1. Submit an application to workplace on behalf of your company.
2. Once your application has been approved, you will receive an email inviting you to join. The response may take a while.
3. From the e-mail invitation, select Get Started.
4. Enter your profile information.

   Tip

   Set yourself as the system administrator. Remember that only system administrators can create custom integrations.

5. Select Preview Profile and verify the information is correct.
6. Access Free Trial.
7. Create a password.
8. Select Invite Coworkers to invite employees to sign-in. The employees you invited will become members as soon as they sign. They will go through a similar sign-in process as described in these steps.

Create a custom integration

Create a custom integration for your Workplace following the steps described below. When you create a custom integration, an app with defined permissions and a page of type Bot (visible only within your Workplace community) are created.

1. In the Admin Panel, open the Integrations tab.

2. Select Create your own custom App.

3. Choose a display name and a profile picture for the app. Such information will be shared with the page of type Bot.

4. Set the Allow API Access to App Settings to 'Yes'.

5. Copy and safely store the App ID, App Secret and App Token that's shown to you. Rar file download for windows 10.

6. Now you have finished creating a custom integration. You can find the page of type Bot in your Workplace community, as shown below.

Update your bot code with Facebook adapter

Your bot's source code needs to be updated to include an adapter to communicate with Workplace by Facebook. Adapters are available for JavaScript/Node.js and C#/.NET bots.

Provide Facebook credentials

To your bot's appsettings.json file, add the Facebook App ID, Facebook App Secret and Page Access Token values that you copied from Facebook Workplace previously. Instead of a traditional page ID, use the numbers following the integrations name on its About page. Follow these instructions to update your bot source code in JavaScript/Node.js or C#/.NET.

Submit Workplace app for review

Please refer to the Connect a bot to Facebook Messenger section and Workplace Developer Documentation for details.

Make the Workplace app public and publish the Page

Please refer to the Connect a bot to Facebook Messenger section for details.

Setting the API version

If you receive a notification from Facebook about deprecation of a certain version of the Graph API, go to Facebook developers page. Navigate to your bot's App Settings and go to Settings > Advanced > Upgrade API version, then switch Upgrade All Calls to version 4.0.

Connect a bot to Facebook using the Facebook adapter

Use the Bot Framework Facebook adapter to connect your bot with Facebook Workplace. To connect to Facebook Messenger, you can use the Facebook channel or the Facebook adapter.Facebook adapters are available for JavaScript/Node.js and C#/.NET bots. Iomega hard drive not responding.

In this article you will learn how to connect a bot to Facebook using the adapter. This article will walk you through modifying the Echo bot sample to connect it to Facebook.

The instructions below cover the C# implementation of the Facebook adapter. For instructions on using the JavaScript adapter, part of the BotKit libraries, see the BotKit Facebook documentation.

Prerequisites

• The EchoBot sample code
• A Facebook for Developers account. If you do not have an account, you can create one here.

Create a Facebook app, page and gather credentials

1. Log into https://developers.facebook.com. In the main menu, select My Apps > Create App.

2. In the dialog that appears, enter a display name for your new app and then select Create App ID.

Set up Messenger and associate a Facebook page

1. Once your app has been created, you will see a list of products available to set up. Select Set Up next to the Messenger product.

2. You now need to associate your new app with a Facebook page—to create a page if you do not have an existing page you want to use, select Create New Page in the Access Tokens section. Select Add or Remove Pages, choose the page you want to associated with your app, and select Next. Leave the Manage and access Page conversations on Messenger setting enabled and select Done.

1. Once you have associated your page, select Generate Token to generate a page access token. Make a note of this token as you will need it in a later step when configuring your bot application.

Obtain your app secret

1. In the left hand menu, select Settings and then select Basic to navigate to the basic settings page for your app.

2. On the basic settings page, select Show next to your App Secret. Acrobat writer for windows 7. Make a note of this secret as you will need it in a later step when configuring your bot application.

Wiring up the Facebook adapter in your bot

Now that you have your Facebook app, page and credentials, you need to configure your bot application.

Install the Facebook adapter NuGet package

Add the Microsoft.Bot.Builder.Adapters.Facebook NuGet package. For more information on using NuGet, see Install and manage packages in Visual Studio.

Create a Facebook adapter class

Create a new class that inherits from the FacebookAdapter class. This class will act as our adapter for the Facebook channel and include error handling capabilities (similar to the BotFrameworkAdapterWithErrorHandler class already in the sample, used for handling other requests from Azure Bot Service).

Create a new controller for handling Facebook requests

Create a new controller which will handle requests from Facebook, on a new api/facebook endpoint instead of the default api/messages endpoint used for requests from Azure Bot Service channels. By adding an additional endpoint to your bot, you can accept requests from Bot Service channels, as well as from Facebook, using the same bot.

Inject the Facebook adapter in your bot startup.cs

Add the following line to the ConfigureServices method within your startup.cs file. This will register your Facebook adapter and make it available for your new controller class. The configuration settings you added in the previous step will be automatically used by the adapter.

Once added, your ConfigureServices method should look like this.

Obtain a URL for your bot

Now that you have wired up the adapter in your bot project, you need to provide to Facebook the correct endpoint for your application, so that your bot will receive messages. You also need this URL to complete configuration of your bot application.

To complete this step, deploy your bot to Azure and make a note of the URL of your deployed bot.

Note

If you are not ready to deploy your bot to Azure, or wish to debug your bot when using the Facebook adapter, you can use a tool such as ngrok (which you will likely already have installed if you have used the Bot Framework Emulator previously) to tunnel through to your bot running locally and provide you with a publicly accessible URL for this.

If you wish create an ngrok tunnel and obtain a URL to your bot, use the following command in a terminal window (this assumes your local bot is running on port 3978, alter the port numbers in the command if your bot is not).

Add Facebook app settings to your bot's configuration file

Add the settings shown below to your appsettings.json file in your bot project. You populate FacebookAppSecret and FacebookAccessToken using the values you gathered when creating and configuring your Facebook App. FacebookVerifyToken should be a random string that you create and will be used to ensure your bot's endpoint is authentic when called by Facebook.

Microsoft Facebook Messenger Scam

Once you have populated the settings above, you should redeploy (or restart if running locally with ngrok) your bot.

Complete configuration of your Facebook app

Microsoft Facebook Messenger

The final step is to configure your new Facebook app's Messenger endpoint, to ensure your bot receives messages.

Facebook Messenger App Microsoft Store

1. Within the dashboard for your app, select Messenger in the left hand menu and then select Settings.

2. In the Webhooks section select Add Callback URL.

3. In the Callback URL text box enter your bot's URL, plus the api/facebook endpoint you specified in your newly created controller. For example, https://yourboturl.com/api/facebook. In the Verify Token text box enter the verify token you created earlier and used in your bot application's appsettings.json file.

4. Select Verify and Save. Ensure you bot is running, as Facebook will make a request to your application's endpoint and verify it using your Verify Token.

5. Once your callback URL has been verified, select Add Subscriptions that is now shown. In the pop-up window, choose the following subscriptions and select Save.

   • messages
   • messaging_postbacks
   • messaging_optins
   • messaging_deliveries

Test your bot with adapter in Facebook

You can now test whether your bot is connected to Facebook correctly by sending a message via the Facebook Page you associated with your new Facebook app.

1. Navigate to your Facebook Page.

2. Select Add a Button.

3. Choose Contact You and Send Message, then select Next.

4. When asked Where would you like this button to send people to? choose Messenger, then select Finish.

5. Hover over the new Send Message button that is now shown on your Facebook Page and select Test Button from the pop-up menu. This will start a new conversation with your app via Facebook Messenger, which you can use to test messaging your bot. Once the message is received by your bot, it will send a message back to you, echoing the text from your message.

You can also test this feature using the sample bot for the Facebook adapter by populating the appsettings.json file with the same values described in the steps above.

See also

• Sample code. Use the Facebook-events sample bot to explore the bot communication with Facebook Messenger.