Community
  • 34.9K Members
  • 2,486 Online
  • 6,558 Conversations
Collaborate, share and learn from experts
Microsoft Tech Community
homepage banner 2
Find sessions, presentations, recordings, and conversations from our free two-day training events.
Get access to the Microsoft Tech Summit content here.
Get started

Recent Conversations

  • 12-24-2016

    We have created some custom SharePoint hosted add-ins and added them on to a Page. These add-ins have some custom styles that are common however, they are not shared.

    Is there a way by which I can put these custom styles in a common location (i.e. outside the add-in web) and access the same file across these different addins? I also dont want to load the shared css file to to be loaded indidvidually for each of the add-ins?

     

    Thanks

    7
    0
  • 12-24-2016

    Do companies closely related to Microsoft have access to technologies us mortals do not have?

     

    IN VisualSPs training product I see non-SharePoint content being displayed on top of Modern Experiences, which, according to the message from Microsoft can not do branding or run script

     

    5
    0
  • in Exchange 
    12-23-2016

    I'm trying to create a transport rule (Exchange Online) to add an image to outgoing emails where the send is a member of a certain group.

     

    I've created the group in AD and performed a delta sync to AAD. I've verified that the group was successfully synced.

     

    Is this possibly a timing issue within Office 365?

     

    Here's the full error:

     

    Couldn't find object "Transport Rule - Banner Type 1". Please make sure that it was spelled correctly or specify a different object.
        + CategoryInfo          : InvalidArgument: (FromMemberOfSmiley Frustratedtring) [New-TransportRule], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : [Server=CY4PR08MB2741,RequestId=79473b50-adad-4cc6-9bfa-cc8f909765ec,TimeStamp=12/23/2016 7:08:57 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2B4C0 
       A88,Microsoft.Exchange.MessagingPolicies.Rules.Tasks.NewTransportRule
        + PSComputerName        : outlook.office365.com

     

    (That's funny. Looks like this forum's emoji parser could use a little TLC.) 

    15
    1

    The group needs to be 'recognizable' by Exchange. You cannot use a regular security group, it needs to be mail-enabled. Or a simple distributiongroup. In other words, it should appear in the list you get with Get-Group or Get-Recipient.

  • 12-23-2016

    I've managed to get myself confused as to how the AD mobile attribute syncs to AzureAD. According to here it's part of the set of attributes that's synchronised, however unlike seemingly everything else it's still allowed to be edited by users or admins through Delve profiles and Admin center.

     

    While I wait to see what happens in my environment, does anyone know what happends, I guess there is no writeback? Is there more than one field ? does the sync data overwrite whats in azureAD ? On change or everytime ?

     

    TIA - Steven

    31
    3

    They all seem to be setting the mobilephone one, and yes, it looks like there is no SOA for this attribute. You can edit it directly even in dirsynced scenarios and changes you make in O365 are not overwritten by dirsync. What I remember is that previously this attribute never made it to SPO, so we had to set it there manually. It has always been a special one Smiley Happy

  • 12-23-2016

    I believe this is a question for @Erwin van Hunen, but any help is appreciated!

     

    I'm working on creating a new cmdlet for PnP to allow the addition of Image Renditions to SharePoint. I've created the Core method in C# and it's compiled and tested successfully from a console app.

     

    I then added the cmdlet to the PowerShell solution, but am experiencing something odd during my testing. I'm guessing it's something I'm doing wrong, but I've not been able to figure out what the issue is and would appreciate some guidance. I'm pretty sure my references are all correct and I'm importing the correct module, but I could be wrong. I've also closed and reloaded new PowerShell sessions throughout my troubleshooting.

     

    The screenshot below is taken after building the Core and PowerShell solutions, then importing the updated module that contains my new cmdlet. My cmdlet name is "Add-PnPPublishingImageRendition." You can see that immediately after I import the module, the cmdlet is listed. However, if I then attempt to use the cmdlet (with or without parameters), I'm told it's not a cmdlet. Following that with another "Get-Command," you can see that my cmdlet is gone. Where'd it go? What am I doing wrong?

     

    pnp-2016-12-23_22-00-11.png

     

     

    23
    0